I am also getting the same problem. We have a route with several routing slips in the
sequence, for selecting appropriate XSL transforms and XSD validations. Also one to
compute a file endpoint destination depends on identity of submitter.
We get consistent behavoiur - the headers survive
On Thu, Oct 18, 2012 at 2:14 PM, Graham Perkins
graham.perk...@workplacesystems.com wrote:
I am also getting the same problem. We have a route with several routing
slips in the sequence, for selecting appropriate XSL transforms and XSD
validations. Also one to compute a file endpoint
On 23 March 2012 16:33, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
You can use the tracer to help see where the headers dissappear
http://camel.apache.org/tracer
And see this FAQ as well
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
Thanks, Claus. This helped me
://camelone.com
FuseSource
Email: cibsen@
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
--
View this message in context:
http://camel.465427.n5.nabble.com/Headers-disappearing
Hi, can I get a quick sanity check before we spend more time investigating?
We're using Camel 2.5.0 and have a setup like this: routing slip -
seda - processor
We set headers in our routing slip, and by the time the message has
hit the processor, the headers have been stripped. Is this expected
Hi
You can use the tracer to help see where the headers dissappear
http://camel.apache.org/tracer
And see this FAQ as well
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
On Fri, Mar 23, 2012 at 1:33 PM, Alex Anderson a...@frontlinesms.com wrote:
Hi, can I get a quick
.n5.nabble.com/Headers-disappearing-in-RoutingSlip-tp5589311p5590286.html
Sent from the Camel - Users mailing list archive at Nabble.com.
