It is some horrible code to automatically create
the destination if it doesn't exist.
But it assumes the name
regardless of the context you specify.
It has already been removed in the jboss4
So do you mean to say that currently, an MDB in JBoss cannot consume a queue that does not start with "queue/" in the JNDI Name ? If I have an application that starts with a context like "jms/" for example, I can not consume this from an MDB ? Are there workarounds for this ?
A simple temporary hack would be to create an alias:
But it needs to be fixed, because both names
The create if it doesn't exist only works with
I've fixed this in the 3.0 and 3.2 branches.
It now tries the specified destination-jndi-name first.
Thanks for changing the default behavour if the queue naming.
I have been reading the posts regarding integration of MQSeries and JBoss (Jboss Forum) with great interest .
Does JBOSS and MQSeries working well together ?
Does all of the information in the Forums posts still apply? Have things changed for jboss 3.2?
I noticed in a post "I Added the following the the jms-service.xml..." this file does not exist in JBOSS 3.2 . I assume the new files are called jms-ds....
Is it still necessary to rebuild JBOSS to get a MQSeriesJMSProvider?
Can this be avoided? There was discussion on the Post as to whether the default adapter should work fine?
Again, in the posts , loshusu said that JMSAdmin can use JBossNS Service directly. I could not make this work??
Sorry for all the questions. However, we are trying hard to make this work.
I have never tried to use MQSeries
You do need a provider so you can tell mdbs
which connection factory to use.
Yes jms-service.xml has had its name changed