On Wed, Nov 4, 2009 at 2:48 PM, mcrive <mcr...@optasportsdata.com> wrote: > > thank you for such a quick reply! > > I am currently using 2.0 REL, is there a way to do the same thing with the > version I have? >
You can use interceptSendToEndpoint http://davsclaus.blogspot.com/2009/05/on-road-to-camel-20-interceptors-round.html And see more details at the Camel documentation (link from above) And then have it decorate with a custom header what the endpoint is. That you can retrieve in your error processor. The intercepted endpoint is stored in the IN message header as: Exchange.INTERCEPTED_ENDPOINT > > Claus Ibsen-2 wrote: >> >> On Wed, Nov 4, 2009 at 2:40 PM, mcrive <mcr...@optasportsdata.com> wrote: >>> >>> I ha following route >>> >>> >>> onException(GenericFileOperationFailedException.class) >>> .process(new DeliveryFailureHandler()).stop(); >>> >>> >>> from("test-jms:queue:feed.notificationtest.queue") >>> .process(processor) >>> .recipientList(header("recipientListHeader").tokenize(",")); >>> >>> >>> recipientListHeader contains a cvs list of endpoints (FTP) >>> how can I detect the endpoint URI causing the exception? >>> -- >> >> What version are you using? This is important to know. >> >> In 2.1-SNAPSHOT you can get it using a property on the exchange >> >> String uri = exchange.getProperty(Exchange.FAILURE_ENDPOINT, >> String.class); >> >> >> >>> View this message in context: >>> http://old.nabble.com/Error-handling-with-recipientList-tp26196454p26196454.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >>> >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> >> > > -- > View this message in context: > http://old.nabble.com/Error-handling-with-recipientList-tp26196454p26196600.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
