i use the JmsMessageID to filter the message and detect if they are
duplicate. I think i get where i do my mistake. Your suggestion to move
idempotentConsumer in the "source" is what i want.
--
View this message in context:
http://camel.465427.n5.nabble.com/Convert-message-into-two-converters-a
What are you using for you expression that generates the messageId? I don’t
see anything in the routes below (in fact, the last route isn’t valid).
Can you explain what sort of duplicate you are trying to avoid? It would seem
that given the same input, the result of converting to object A or B
Let me make it more clear because i am not only send the message to the
queue.
So basically my two sub-routes use somehow the same idempotent repository. I
want basically the incoming message to copy it se
I’m not following your logic in this route - both of the sub-routes are using
the same idempotent repository, so I think you’ll wind up marking items as
duplicates when they really are not.
Did you mean to put the idempotent consumer on the from=source route?.
> On Jul 20, 2016, at 3:42 AM, red
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
I don’t think multicast will do what you’re after - it sends the same message
to multiple endpoints.
I think you could accomplish what you’re after using three routes:
> On Jul 19, 2016, at 7:21 AM, redpower1989 wrote:
>
> Maybe i could make it mo
Maybe i could make it more clear. Can i use multicast with too converters ?
Something like that
I am trying that but i get the message to be converted only to typeB. Is
there any possible way to copy the message convert it to A and B and sen
