The jbi exchanges can be sent over the jms flow, at the obious condition
that
they can be serialized. Some components, like the quartz component or
the jms binding put non serilizable data in the exchange, so that they can
currently not be used with the jms flow.
See https://jira.logicblaze.com/jira/browse/SM-178
Cheers,
Guillaume Nodet
John Sloan wrote:
Just to experiment with a flow other than SEDA, I naively
tried
flowName="jms?jmsURL=reliable:tcp://localhost:12345"
for both my application and the loan-broker example. Both
serices catch a NotSerializableException when serializing (if I'm
interpreting the stack trace correctly) the ConcurrentHashMap
in the NormalizedMessage in the ActiveMQMapMessage when trying
to send a new InOut MessageExchange to a peer on the ESB.
I'm assuming this is pilot error on my part. Is there some
magic when using the JMS or cluster flows, perhaps something
I need to change in my application, or in the activemq.xml
configuration?
Thanks...
