.com/Using-correlationid-to-isolate-jms-queues-in-multiple-camelContexts-tp5719202p5719247.html
Sent from the Camel - Users mailing list archive at Nabble.com.
gt;
> I understand that JMS endpoints were designed to execute in the *actual
> behavior*. But in this case, I need to run *my desired *behavior.
>
> There´s a way to do this using correlationIds (not send/receive approach)?
>
> Thanx a lot
>
>
>
> --
> V
ehavior* is:
> > - Messages produced in #a sometimes is consumed in c# and sometimes in d#
> > - Messages produced in #b sometimes is consumed in c# and sometimes in d#
> >
> > I understand that JMS endpoints were designed to execute in the *actual
> > behavior*. But in this case, I need to run *my desired *behavior.
> >
> > There´s a way to do this using correlationIds (not send/receive
> approach)?
> >
> > Thanx a lot
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/Using-correlationid-to-isolate-jms-queues-in-multiple-camelContexts-tp5719202.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
to execute in the *actual
> behavior*. But in this case, I need to run *my desired *behavior.
>
> There´s a way to do this using correlationIds (not send/receive approach)?
>
> Thanx a lot
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Using-correlationid-to-isolate-jms-queues-in-multiple-camelContexts-tp5719202.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
-isolate-jms-queues-in-multiple-camelContexts-tp5719202.html
Sent from the Camel - Users mailing list archive at Nabble.com.
