i have to create a route that sends a message (SOAP) multiple times to same
endpoint. The only difference in message is that one attribute (xml, set) is
different.
At the moment i am using multicast for this:
MulticastDefinition multicast = rtdmProcess.multicast();
// loop over event names to use same data for every target
event
// and send it to rtdm
for (String eventName : rtdmTargetEvents) {
multicast.process(rtdmSetNameFactory.get(eventName)).to(rtdmEndpoint);
}
So the endpoint receives the same message multiple times but with different
event names. This seems to work fine with cxf endpoint.
But things get odd if i add "parallelprocessing()" or if i test it with a
MockEndpoint.
In case of parallelprocessing the mapping of messages and names seem to be
shuffled: if i send 2 messages m1 and m2 and want them to be multicasted to
event name N1 and N2 then m1 will be sent twice to N1 and m2 will be sent
twice to N2.
In case of using MockEndpoint without parallel processing all messages will
only be sent to the second last name set. In this case the set name seems to
be called on the same exchange again and again and not on copies. The second
(and all after) call of set name receives an exchange with the name already
set.
Is this working as intended?
Is there probably a better pattern to be used in this case?
--
View this message in context:
http://camel.465427.n5.nabble.com/sending-nearly-same-message-multiple-times-to-same-endpoint-tp5757187.html
Sent from the Camel - Users mailing list archive at Nabble.com.
