JBossMQ uses jndi to lookup administered JMS objects, such as Queue and Topic.
The jndi or jnp of JBoss uses Unix-like file system to store objects.
queue/ , in this case, indicates a directory name containing various queues names.
hope that helps
Thanks for trying, but that tells me what JBossMQ does, not why the message-driven bean plugin assumes that queues will be prefixed with the queue/ directory.
It seems an assumption was made that the MDB would never be used with another messaging system. It would have been better to take the value of the destination-jndi-name element of the jboss.xml deployment descriptor as-is. People who are running against JBossMQ would need to prefix their destinations with "queue/" or "topic/", but it would open the door to other messaging systems.
I guess I'll take a shot at making the change myself and see how it works.
It was done totaly pluggable from start. Then someone introduced sopme magic when a destination was not there and the code became unportable. If you solve this, pleas contribute a patch.
> It was done totaly pluggable from start. Then someone
> introduced sopme magic when a destination was not
> there and the code became unportable.
Yeah, you need some kind of quality control (a 'board' or whatever). Contributing a change over a change doesn't work.
Yea, but that particular change WAS much depated an introduced against mine and Hirams recomendation. I do not want to dvelve into it; but I did lose the lust to fix the problem.