Re: Convert message into two converters and dilliver them to one destination

[redpower1989]

Thanks for answer. Does anyone know if you can change the messageId when you
are using multicast? At the moment multicast copy the message and the new
two messages have the same message ID. If i have a idempotentConsumer before
a producer endpoint it will block my second message even if it has been
converted to something different. For example:


<route>
  <from uri=“{{source}}” />
  <multicast>
    <to uri=“direct:a” />
    <to uri=“direct:b” />
  </multicast>
</route>

<route>
  <from uri=“direct:a” />
  <convertBodyTo type=“objectTypeA” />
<idempotentConsumer messageIdRepositoryRef="myRepo" skipDuplicate="false">
  </idempotentConsumer>
  <to uri=“activemq:FOO.BAR” />
</route>

<route>
  <from uri=“direct:b” />
  <convertBodyTo type=“objectTypeB” />
  <idempotentConsumer messageIdRepositoryRef="myRepo" skipDuplicate="false">    
                     
</idempotentConsumer>
  <to uri=“activemq:FOO.BAR” />
</route>



--
View this message in context: 
http://camel.465427.n5.nabble.com/Convert-message-into-two-converters-and-dilliver-them-to-one-destination-tp5785205p5785266.html
Sent from the Camel - Users mailing list archive at Nabble.com.