Well - that's how camel works. It will go through each element in the route.
2011/8/24 dougman82 <[email protected]> > I've already got trace enabled. I can watch the message go through the > route, and hit the validator endpoint - which shows that it successfully > validates. And then nothing. What it seems like is that Camel assumes that > since the validator is the last endpoint, that validation is all I want to > have happen at the end of the route. > > For now, just to make it work, I am sticking with inserting a "bean" > endpoint after the validator, where a dummy method is called that just > promptly returns the message. Obviously, I am open to a more robust > solution, but this works for now. > > Thanks, > Doug > > > > On Tue, Aug 23, 2011 at 4:03 PM, David J. M. Karlsen [via Camel] < > [email protected]> wrote: > > > Try enabling trace: http://camel.apache.org/tracer.html. > > One of your route steps might be throwing an exception which is dealt > with > > by a default error handler: > > http://camel.apache.org/error-handler.html > > > > 2011/8/23 dougman82 <[hidden email]< > http://user/SendEmail.jtp?type=node&node=4728571&i=0>> > > > > > > > Hello all, > > > > > > Just to be quick, I've got a camel route that looks something like > this: > > > > > > <route id="myRoute"> > > > <from uri="blahblah" /> > > > <to uri="anEndpointThatGivesAResponse" /> > > > <to uri="xslt:/path/to/transform" /> > > > </route> > > > > > > Basically, a message is delivered to an endpoint and a response is > > received > > > which is then transformed using an XSL stylesheet, and the result is > > given > > > back to the original requester. This works just fine. > > > > > > My new requirement is to add an XML schema validation step: > > > > > > <route id="myRoute"> > > > <from uri="blahblah" /> > > > <to uri="anEndpointThatGivesAResponse" /> > > > <to uri="xslt:/path/to/transform" /> > > > <to uri="validator:/path/to/schema/file" /> > > > </route> > > > > > > When I add that last step to the route, the XML message is successfully > > > validated, but in the process, the message gets eaten. It seems that > the > > > validation step stops the route, and the original requester gets > nothing > > > back. > > > > > > I'm hoping I have overlooked something very basic about Camel. Any > > > thoughts? > > > > > > By the way, I am using Camel 2.6 with Spring 3.0.5. > > > > > > -- > > > View this message in context: > > > > > > http://camel.465427.n5.nabble.com/Camel-Validator-Eats-the-Message-tp4728003p4728003.html > > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > > > > > > > > -- > > -- > > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen > > > > > > ------------------------------ > > 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-tp4728003p4728571.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-tp4728003p4730723.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
