MDB's require an associated JMS resource when deployed to the server, otherwise,
deployment will fail.

For zero-configuration deployment to work nicely, that means that when an MDB is
created, the associated server plugin is notified to also create any necessary
resources or other artifacts.

However, the user might already have a JMS Resource they wanted to use, for
example, it might be a preexisting shared resource already deployed on the server.

So I propose we have a mechanism to let the user signify they want (or don't
want) the associated server to create the required resources.  The obvious way
to do this is to add a check box (defaulting to checked) such as:

    [x] Create Server Resources

If the user leaves this checked, then the wizard calls
"ensureResourceDefinedForEjb()" (it does this today).  If it is not checked,
then the wizard does not make this call.

There is also another possibility, but it might be too much overloading of
information.  We could assert that if the user fills in the mapped name in the
wizard, that it is assumed to represent an existing resource (or the user is
responsible for creating a resource with that name manually).  If mapped name is
not filled in, then the server plugin would create a JMS Resource for the MDB
and set the server specific jndi-name to refer to that resource.  I don't like
this alternative very much, but it's another option.