THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Note |
|---|
Under Construction |
| Anchor | ||||
|---|---|---|---|---|
|
The primary actors and their general goals
Actor | Goal |
|---|---|
Client (Browser) | |
Developer |
|
Framework (System) |
|
Container |
|
Extension (Plug In) |
|
... | Anchor | ||||
|---|---|---|---|---|
|
Business Use Cases (end user applications)
Priority | Goal | Story or Brief | Issue ID | |
|---|---|---|---|---|
| Client | Client can submit a request and receive a customized response. |
| |
| Framework | A request can invoke a pluggable handler written as a server-side class. |
| |
|
|
| |
|
|
|
|
|
|
| Anchor | ||||
|---|---|---|---|---|
|
Development Use Cases (application developers)
Priority | Goal | Story or Brief | Issue ID | |
|---|---|---|---|---|
| Developer | How to create an Action class |
| |
|
|
| |
|
|
|
|
|
|
| Anchor | ||||
|---|---|---|---|---|
|
Framework Use Cases (framework developers)
Priority | Goal | Story or Brief | Issue ID | |
|---|---|---|---|---|
| Developer | How we configure actions using conventions and annotations |
| |
|
|
| |
|
|
|
|
|
|