[jboss-dev-forums] [Design of JBoss ESB] - Re: DefaultJMSPropertiesSetter, DefaultESBPropertiesSetter a

[beve]

anonymous wrote : But should this not be the responsibility of the gateway and EPR to handle? 
Well I though that would not be needed. Filtering this out when a message enters at the gateway would work if there was only one provider in the bus. The ESB Message could never contain the the filtered out property and this would not be set on the jms message being sent internally, be it by the courier, or an outbound jms router. 

anonymous wrote : This was seen with a single provider, oracle, we were not passing these between different providers. 
If it's the same provider it should not have this problem. What am I missing ? :)

anonymous wrote : Do you have any examples of the properties which you are allowed to set? 
Any property not starting with 'JMS' is considered an application property. 

I really think that we should not filter at all and that it's strange that a jms provider can choose to reject another vendors properties like this. I would have thought that they would simply pick up the ones they are is interested in and ignore the others. I also thought that all jms header properties could be used in message selectors which would be another reason not to reject properties like this. But this is only my view of this matter. There might be other things to consider about this and perhaps rejecting is a valid implementation choice.

/Daniel

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

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230874