To clarify, your route flows from the initial consumer (jetty), to a remove
step, then transform, then a "direct" route consisting of another transform,
and then a log().
All through this sequence, you have an IN body going from step to step
(sometimes being transformed, but still IN when it reaches the next step in
the route).
The OUT would be the response that would be returned all the way back to
whatever software entity made the initial request via to your jetty
consumer. But, that OUT is not being set at any point. You could have a
processor that sets the out.body
Another point to remember is that when you're logging, ${body} is a synonym
for ${in.body}. You can use ${out.body} to log the body of the OUT (but that
will be blank in your particular example).
--
View this message in context:
http://camel.465427.n5.nabble.com/Can-t-understand-what-inOnly-is-doing-tp5787961p5787977.html
Sent from the Camel - Users mailing list archive at Nabble.com.
