One point I should add is that I am not using JBossMQ for my queue, I am using an Oracle Advanced Queue.
JBoss's MDB has nothing to do with JBossMQ.
You declare the queue by adding destination-jndi-name to your mdb in jboss.xml
see docs/jboss-3.2.dtd for more info
The jboss-3.2.dtd gives no applicable information other than that the destination-jndi-name exists for MDBs, which I was already aware of (see my original post). What is not clear is how JBoss can make the connection between the JNDI name I specify in the destination-jndi-name entry and the actual queue which is being provided by an Oracle database. From what I can tell the destination-jndi-name entry just gives JBoss a logical name of where to look in JNDI for the queue that the MDB should listen on, but it does nothing in the way of actually binding a queue to that JNDI name. Isn't this what I need to do next ?
Thanks in advance for any insight.
i believe the answers you are looking for can be found here:
1/2 way down the first page you will see an post for configuring an mdb to connect to a remote queue, and on page 2 at the top, you will find information on connecting to oracle in specific. [/url]