This is the first in several use cases in support of CRUD for topics and queues. Comments are welcome.
USE CASE 1: View a list of Destinations
Basic Description
An administrator uses the system to view information on existing destinations.
Goal
Display a list of destinations including queue and topic types.
Basic flow of events
1. The user indicates to the system that they wish to view a list of all existing destinations.
2. The system displays a list of destinations of queue and topic types.
3. The use case ends.
Extension points
E1.1: Refresh the list
After step 3) in the Basic Flow:
1. The user indicates to the system that they wish to refresh the list of destinations.
2. The system re-checks the current state and displays a new list of destinations.
3. The use case ends.
Alternate flows
A1.1: View a List of Queue Only
During step 1) of the Basic Flow:
1. The user indicates to the system that they wish to view only a list of queues.
2. The use case rejoins the Basic flow at step 2).
A1.2: View a List of Topic Only
During step 1) of the Basic Flow:
1. The user indicates to the system that they wish to view only a list of topics.
2. The use case rejoins the Basic flow at step 2).
Special Requirements
1. The minimal information of a destination to display should include:
a. Queue/Topic name
b. JNDI name
c. Status, e.g. Started.
