"beve" wrote : Actually thinking about this I don't think so and the best option would probably to be filter out all provider/vendor specific properties that start with JMS_, Okay, that makes things easier to handle in that case. "beve" wrote : and do the same with all jms defined properties starting with JMSX except for JMSXGroupID and JMSXGroupSeq which are standard properties clients should use if they want to group properties. These two are the only JMSX properties that clients can set as far as I know. The JMSX ones are already handled by the DefaultJMSPropertiesSetter and it would be simple enough to add the JMS_ ones to that. "beve" wrote : After wasting some of your time and basically re-stating your suggestion in your original post I think so :) This is not a waste of time :) Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231001#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...