JBossMQ and JBoss Messaging queue deployment descriptors are in-compatible.
The application deployment descriptors are incompatible? I thought that they were as my ejb-jar.xml and jboss.xml haven't been modified because from what i understand i shouldn't have to?
the destination deployment descriptors are incompatible - see destinations-service.xml for examples of JBoss Messaging destination deployment descriptors.
Hmm, not sure if i made it clear the queues and topics all deploy without error so that leads me to believe that the ServerPeer and post-office are all working together.
Now when i deploy the application that deploys just fine in JBossMQ; with the same destinations defined in JBoss Messaging the application fails to deploy because the delegates are indicated that the queues/topics do not exist. No the exception does indicate that the queue/topic does not exist. However when i look at the JMX console they are indeed there.
So I would actually be curious to know if there is something to do with when the error occurs it doesn't use the full JNDI name. Cause the error says that a destination doesn't exist but doesn't include the /queue prefix?
OK, well I do believe i am closer. It is now a more of question why this occurs ?
My JBoss Messaging Configuration had a seperate PostOffice, ServerPeer, UserManager, and PersistenceManager. They were all deployed/registered in the standard com.xxxx. object domains. All of these components appeared to have deployed correctly and without contention when the application EAR was not deployed.
I changed the dependencies of my queues and topics to the jboss.messaging: server peers and post-office and the application now deploys without error and is processing data.
My question is why am i not able to have my own PostOffice and ServerPeer as the Dependants of my own queues and topics. (and yes i do have a different ID than 0). It appears the JBoss Messaging supports multiple instances so i am not sure why this occurs?