n context:
> http://camel.465427.n5.nabble.com/Camel-Bean-Component-Behaviour-in-case-of-an-InOut-exchange-tp5721888p5722364.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib..
.nabble.com/Camel-Bean-Component-Behaviour-in-case-of-an-InOut-exchange-tp5721888p5722364.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.465427.n5.nabble.com/Camel-Bean-Component-Behaviour-in-case-of-an-InOut-exchange-tp5721888p5721963.html
Sent from the Camel - Users mailing list archive at Nabble.com.
got started.
As a workaround you can try adding a 2nd step to the route
from JMS
bean XXX
to log:foo
Eg just to a log or something, eg so the route has 2+ steps.
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Bean-Component-Behaviour-in
-in-case-of-an-InOut-exchange-tp5721888p5721926.html
Sent from the Camel - Users mailing list archive at Nabble.com.
>
What version of Camel are you using?
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Bean-Component-Behaviour-in-case-of-an-InOut-exchange-tp5721888.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibse
d up getting X on my reply queue which is my original
request not my response. Am I missing something here?
Regards,
Sushil
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Bean-Component-Behaviour-in-case-of-an-InOut-exchange-tp5721888.html
Sent from the Camel - Users mai
