Hi Willem, Thanks for your comments! Yes, the delivery of the message failed. I've now moved the endpoint-options as you suggested and got rid of the "bridgeEndpoint", as we use the HTTP_URI header.
Now it works! Thanks a lot! Reinhard -----Original Message----- From: Willem jiang [mailto:[email protected]] Sent: Dienstag, 6. November 2012 05:57 To: [email protected] Subject: Re: HTTP component: Handling error codes Can you check the log to see if the camel route is failed to redelivery the message? I don't think you set right http endpoint option rightly with the HTTP_QUERY header, as it will not effect the behavior of camel-http endpoint. Can you setup the camel-http endpoint like this ? > .to("http://dummyHost?bridgeEndpoint=true&throwExceptionOnFailure=false") -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: willemjiang On Tuesday, November 6, 2012 at 12:21 AM, Reinhard Prechtl wrote: > Hi there, > > I'm maintaining an existing camel based solution that integrates a REST based > web-service. Right now I face the problem, that in case of a non 200 HTTP > response, the route doesn't execute past the http-component, meaning > processors after the http-component are not called. > The HTTP component has the "throwExceptionOnFailure" parameter set to > "false", as far as I understand this should result in a continued route > execution after a 400 error code (in my case). > > Here's the route: > > from("cxfrs://bean:restServer") > .process(someProcessorBeforeHttpComponent) > .setHeader(Exchange.HTTP_QUERY, > simple("bridgeEndpoint=true&throwExceptionOnFailure=false")) > .setBody(Builder.simple("")) > .to("http://dummyHost") > .process(someProcessorAfterHttpComponent); > > "someProcessorAfterHttpComponent" isn't executed anymore. > > How come, any ideas? > > Thanks for you inputs! > > Cheers, > Reinhard
