After some thought, I consider this a bug in Spring - Spring is making 
assumptions about how a particular JMS provider implements its destinations 
which is incorrect.

I suggest pinging the Spring team and lodging a bug report with them.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074062#4074062

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074062
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to