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.
