you can define the queue jndi name in jboss.xml descriptor.
as far as creating queues is concerned, you can do it in jbossmq-destinations-service.xml
Hope this is what you are asking for
Thanks, after some reflection (and a peek at the Monson book workbook notes for JBoss 3.0), it dawned on me why a little of this is in the ejb-jar.xml, and the important parts are in vendor-specific files.
Basically, EJBs need a vendor-neutral way to interact with JMS and other container-managed components (like JDBC), but containers don't get the same consideration, since they are vendor-specific by definition.
MDBs don't need to know the topic or queue which they are servicing, so that's not in ejb-jar.xml. They need a way to reference topics or queues to which they send messages, so they use <resource-ref> entries in ejb-jar.xml. In all cases, the deployer has to put info in the vendor-specific deployment descriptor files which can match up with what's in ejb-jar.xml, e.g. define the JNDI JMS name to be used as input for an MDB, or to be connected to a <resource-ref> name used by the MDB.
Not really intuitive, but logical.