Hi Trev Thanks for the pointer. Yes to transform and no .to is the pattern to return a custom response to the caller instead of routing to a new endpoint. I will try to remember to add some wiki doc about this scenario.
Thanks for reporting and digging real deep into Camel to provide good feedback. /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/ On Tue, Nov 25, 2008 at 9:34 AM, Trevv <[EMAIL PROTECTED]> wrote: > > > Claus Ibsen-2 wrote: >> BTW: As I am interesting in improving the documentation could you >> maybe help me out here. On which page/section on the wiki would you >> expect a sample for in out style? > Possibly http://activemq.apache.org/camel/exception-clause.html . > > The problem was that all the exception handling examples, on that page > and on other pages, end with '.to("some endpoint")' to specify where > the failure responses will go; I didn't know what endpoint I could put > inside the '.to("")' in order to get the failure responses to go back > to the same consumer that originally created the exchange. > > It took a few days to realize that I could omit the ".to()" and replace > it with a ".handled()" and a ".transform()" to get the right behavior. > -- > View this message in context: > http://www.nabble.com/HttpProducer%3A-how-to-access-the-body-of-an-error-page--tp20475651s22882p20677003.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
