DefaultESBPropertiesSetter now includes the ability to filter some of the properties as they are imported from JMS, but the current implementation is only usable in certain circumstances. One area which cannot use the mapping is the JMSCourier, as the creation of the Setters are defaulted. I have been helping someone get this to work on Oracle AQ (10.2.3) which does not allow JMS_OracleXXX properties to be set (although 11g does). Tracking this through shows that we can filter on the gateway but, when the listener obtains the ESB aware message through the courier, these headers are reintroduced. So the questions I have are - why does the ESB aware need to handle property mappings? - should the DefaultJmsPropertiesSetter also be filtering? - should we be ignoring JMS_XXX on a global basis? Any thoughts? Thanks Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230834#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...