Send JMS UI

The motivation is described in Resource Reference Binding document.
Briefly, we would like a user to provide a message destination which can be found in the active project or on the server. User can also select a destination bound to a MDB found in any open project. User may also create a new message destination.

Use Case

Basic Flow

1. User invokes "Send JMS Message" action.
2. User selects a destination from the list of available destinations. (A2, A3)
3. User hits 'OK' button. The destination is used in the generated Java code.

+-----------------------------------------------------------------------+
| Send JMS Message                                                      |
+-----------------------------------------------------------------------+
|                                                                       |
| (o) Project Destinations: |_SampleProjectDestination___|_v_| |Add...| |
|                                                                       |
| ( ) Server Destinations:  |_SampleServerDestination____|_v_|          |
|                                                                       |
| ( ) Message Driven Bean:  |_Sample MDB_________________|_v_|          |
|                                                                       |
|             Destination:  |_SampleMDBDestination___________|          |  <-- read-only text field
|                                                                       |
| + Service Locator Strategy------------------------------------------+ |
| |   (o) Generate Inline Lookup Code                                 | |
| |   ( ) Existing Class |_________________________________| |Browse| | |
| +-------------------------------------------------------------------+ |
|                                                                       |
|                                            | OK | | CANCEL | | HELP | |
+-----------------------------------------------------------------------+

Alternative Flow A2

• A2. If there is no suitable destination, user may create a new one.
  • A2.1. User hits 'Add...' button besides the 'Project Destinations' combobox. The 'Add Message Destination' dialog pops up.
  • A2.2. User provides a unique destination name.
  • A2.3. User selects the destination type - Queue or Topic.
  • A2.4. User hits 'OK' button. The flow returns to the step 2, the created destination is selected.

+-----------------------------------------------------------+
| Add Message Destination                                   |
+-----------------------------------------------------------+
|                                                           |
| Destination Name :     |________________________________| |
|                                                           |
| Destination Type :     (o) Queue                          |
|                        ( ) Topic                          |
|                                                           |
|                                | OK | | CANCEL | | HELP | |
+-----------------------------------------------------------+

Alternative Flow A3

• A3. User selects a destination that some particular MDB is listening to.
  • A3.1. User selects a MDB from the list of MDBs. The message destination the MDB is listening to is displayed.
  • A3.2. The flow returns to the step 2, the destination of the MDB is selected.