OpenCms-Struts - OpenCms-Struts Use-Case UC4

Date	Revision	Description	Author
1/23/2003	0.9	Initial Draft	Kenneth Lewelling
4/4/2003	0.91	Converted document to xml for use with Maven.	Kenneth Lewelling

Goal in Context:	Add an action mapping definition to the Struts configuration file and have a corresponding "Action" resource added to the VFS.
Preconditions:	Actor's OpenCms user account is in the Admin group and has read-write permissions on the Struts application.
Successful End Condition:	The Struts configuration file is saved and a new "Action" resource is added to the VFS.
Failed End Condition:	The Struts configuration file is unchanged and no new "Action" resource is added.
Primary Actor:	Struts Developer
Trigger:	Actor adds a action mapping definition in a Struts configuration file.

Actor saves the configuration file.
Configuration file is parsed and checked for errors.
The action mapping definition's path property is checked against a list of all "Action" resources belonging to the Struts application.
If an "Action" resource is not found that corresponds with an action mapping definition's path property a new "Action" resource is added to the VFS. The "Action" resource will take the property path's name and be associated with the Struts application the configuration file is for.
Struts is restarted.
The actor is forwarded to the Struts Administrative View.

1a. The Actor cancles the configuration file changes.

1aa. No changes the the configuration file or the VFS are made.

2a. Errors are found in the configuration file.

2aa. The actor is notified.

2ab. The actor is returned to step 1 and given the opportunity to correct any changes.

4a. If an action mapping definition is resolved to an "Action" resource that is associated with another Struts application the actor is notifed.

4aa. The actor is return to step 1 and given the opportunity to make the required changes.

There are no sub-variations.

Super Ordinate Use Case: UC6 Edit Struts Configuration File

Subordinate Use Case:

None.