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

[Kevin.Conner@jboss.com]

"beve" wrote : 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.
Sure, the ESB message would not contain it and we would not set it but the provider may :)

"beve" wrote : If it's the same provider it should not have this problem. What am I missing ? :)
- Gateway reads message, transforms it (removing properties) and sends it to ESB listener.
- Oracle attaches the properties on sending.
- Listener reads message and, as it has no filter, attaches JMS_Oracle properties to ESB message
- We then send this message, then attempting to set banned properties.

So the properties always exist in Oracle, but are read-only.

"beve" wrote : Any property not starting with 'JMS' is considered an application property. 
Sorry, I was asking for examples of those which start with JMS_.  Are there any which we would want to initialise?

"beve" wrote : 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.
Well, the issue is what we pull into the ESB message and then set on outgoing messages, not really selectors.  The reading of these properties are not prevented, but the setting of them is.

Perhaps we need to flip this on its head, have a set of provider specific *writeable* properties in the EPR to cover read-only *and* providers which do not ignore properties from other providers.

Kev


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

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