camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From atte <atte.he...@gmail.com>
Subject Re: Weird behaviour with message routing
Date Wed, 20 Apr 2011 06:19:24 GMT
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?

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.

Mime
View raw message