If one creates new Message Driven EJB there is a possibility to create a new destination. This destination is created as
a GlassFish resource. The resources are created with an error: all automatically created destinations are linked to the
same physical queue. The effect is that if user creates more than one MDB than they are all connected to the same queue
when deployed in glassfish.
Because user isn't asked to enter physical queue name it can be very annoying to find out, that messages aren't
correctly routed after deploying a project in GlassFish.
The wizard for creating MDBs should ask for physical queue name or generate unique physical queue names based on MDB name.
From EJB point of view it seems that managing of message destinations is too much server dependent. Troubles which you are facing for GF are not valid i.e. for WebLogic. So finally I don't think that it's good idea to create there any server dependent wizard for it.
If I'm not wrong, for EJB application should be important just the JNDI name and the rest - real Queue or Topic for the resource provides the server.
I'm moving to GF component and please Vince evaluate that from your point of view. Probably you could generate unique physical queue/topic for every "virtual".
Some old 6.x request for enhancement. I don't think we have time to implement this in near future. Moving to RFE queue.