On Wed, Apr 20, 2011 at 8:19 AM, atte <atte.he...@gmail.com> wrote:
> Is the consept of my route ok?
>
> .from("quartz").to("http").to("xslt").to("http");
>
> Should I be able to do that?
> Why does the route get broken if I f.ex. add .wireTap to the route?
> .from("quartz").to("http").wireTap("file").to("xslt").to("http");
>
> Is it becouse http endpoint produces a Stream as the body and once the
> stream is read, it is no longer available. Atleas this is how I see it. How
> do I get past this limitation?Yeah the wire tap will copy the message body. So you end up reading the stream multiple times. So try enabling stream caching http://camel.apache.org/stream-caching.html > > Thanks! Any help is appreciated! > > -Atte > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Weird-behaviour-with-message-routing-tp4312978p4315029.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com CamelOne 2011: http://fusesource.com/camelone2011/ Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
