JMS - Destinations - Use case 3
This is the third of several use cases in support of CRUD for topics and queues. Comments are welcome.
USE CASE 3: Create a Destination
Basic Description
An administrator uses the system to add a new destination to a JBoss server.
Preconditions
It is assumed that Use Case 1 will already have been executed and the user has indicated which type of destination, i.e. queue or topic, is going to create.
Goal
A destination of a specified type (queue or topic) is successfully created.
Basic flow of events
1. The user indicates to the system that they wish to create a new destination of either queue or topic type.
2. The system displays a destination attribute fields for the user to fill in.
3. The user fills in the fields and indicates to the system to create a destination with the given settings.
4. The system takes the information entered by the user, validates it and creates a new destination of the specified type.
5. The system indicates to the user that the destination was successfully created.
6. The use case ends.
Alternate Flows
A4.1: Information validation fails, destination not created
During step 4) of the Basic Flow:
1. The system finds a problem with the information the user submitted.
2. The system displays the information the user submitted and indicates to the user which piece(s) of information caused the problem.
3. The use case ends.
A4.2: Information validation fails, user fixes problem
After step 2) of Alternative Flow A4.1:
1. The user updates the pieces of information which the system indicated had caused the problem and indicates to the system to create the destination.
2. The system takes the information entered by the user, validates it and creates the destination.
3. The system indicates to the user that the destination was successfully created.
4. The use case ends.
A4.3: User cancels creation
During step 3) of the Basic Flow:
1. The user indicates to the system that they want to cancel the creation of a destination.
2. The system does not attempt to create a destination. The system displays the page the user was on before attempting to create the destination.
3. The use case ends.
Special Requirements
1. Different attributes can be entered depending upon the type of the destination being created, i.e. queue or topic. The precise breakdown of attributes by type is listed in the reference documents - queue_elements.xls and topic_elements.xls).
2. A destination created through the system must persist across restarts of the JBoss server.