Hi, Thanks for replying - I am using 3.2.1 at the moment. The reason I am using the endpoints I am is because they were the ones that maven put in for me... Being new to this I just assumed that it was the right way to go. Ok guess not.
Another reason that I didn't stray too far from the path on this one is that I had already looked at the new endpoints page, and the only info on the Provider endpoints is that there is no info ;-(. Setting the JMSXGroupID as a simple property in the normalised message, does indeed work and that is what I did to prove the concept - but in a service engine elsewhere in the system. However I felt really that the best place for it was the marshaler as stuff like this shouldn't be part of a service engine elsewhere in the process. Anyway I shall have a go at stumbling through the new endpoints and implementing that marshaler. Thanks & Regards, Paul. Gert Vanthienen wrote: > > Paul, > > > On second thought, another option might be to use the > JbiConstants.PROTOCOL_HEADERS. If you set this property on a > NormalizedMessage to contain a Map, the key-value pairs in that map will > be added to JMS Message as properties. So, if you could add a Map to > the NormalizedMessage that contains the JMSXGroupID with the > corresponding value (e.g. using a servicemix-bean POJO), that might work > just as well. > > > Gert > > > > Gert Vanthienen wrote: >> Paul, >> >> >> ServiceMix 3.2 comes with a few new JMS endpoints (cfr. >> http://servicemix.apache.org/servicemix-jms-new-endpoints.html). The >> consumer and provider endpoints have specific Marshaler interfaces >> (JmsConsumerMarshaler and JmsProviderMarshaler) that are a lot easier >> to implement. >> If you're stuck with ServiceMix 3.1 somehow, your options are probably >> limited to either implementing the JmsMarshaler interface yourself or >> take a look at the source for DefaultJmsMarshaler and make sure that >> you override all methods that use the 'endpoint' field. >> >> >> Gert >> >> >> >> >> PM wrote: >>> Hi, >>> >>> I was planning on subclassing the DefaultJmsMarshaler in order to >>> set the >>> JMSXGroupID into my outbound JMS messages. >>> >>> Would this be the right place to do it? There is nowhere else >>> really in >>> my chain of events that seems sensible to do it. >>> >>> The only problem is that the DefaultJmsMarshaler wants a >>> JmsEndpoint in >>> the constructor. How would I go about providing that? >>> >>> Regards, Paul. >>> >> >> > > > > ----- > --- > Gert Vanthienen > http://www.anova.be > -- View this message in context: http://www.nabble.com/JMSXGroupID-and-where-to-set-it-tp15306955s12049p15333848.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
