Thanks, Christian! That works nicely and looks more elegant than my stopgap solution. And your explanation makes sense. I was kind of figuring that was the behavior, but wasn't fully putting two and two together.
Have a good day, Douglas On Wed, Aug 24, 2011 at 9:07 AM, Christian Mueller [via Camel] < [email protected]> wrote: > Hey Douglas! > > Sorry for the wrong sampe. I was in a hurry... > > <route id="myRoute"> > <from uri="blahblah" /> > <to uri="anEndpointThatGivesAResponse" /> > <to uri="xslt:/path/to/transform" /> > <to uri="validator:/path/to/schema/file" /> > <transform><simple>${body}</simple></transform> > </route> > > Should work for you. > > The reason for this behavior is, that Camel returns the out message of the > last component. Because the validator didn't provide a response (out > message), we have to have an additional component which copies the in > message into the out message... > > Hope this solves your problem. > > Best, > Christian > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Camel-Validator-Eats-the-Message-tp4728003p4730954.html > To unsubscribe from Camel Validator Eats the Message, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4728003&code=ZG91Z21hbjgyQGdtYWlsLmNvbXw0NzI4MDAzfDEzNjg4OTcxNDA=>. > > -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Validator-Eats-the-Message-tp4728003p4731127.html Sent from the Camel - Users mailing list archive at Nabble.com.
