Clearly the extra sem-colon is a bug.
But regarding the issue of not allowing JMSX properties to be set:
The JMS spec (1.1, section 3.5.8, table 3.3) makes it clear that the only JMSX properties
that can be set by the client are JMSXGroupID and JMSXGroupSeq.
So I think the current behaviour is correct.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131050#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...