You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/10/10 10:28:45 UTC

[jira] [Resolved] (CAMEL-6845) Using recipient list to a route that has no error handler should allow caller route to trigger its error handler

     [ https://issues.apache.org/jira/browse/CAMEL-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-6845.
--------------------------------

    Resolution: Fixed
      Assignee: Claus Ibsen

> Using recipient list to a route that has no error handler should allow caller route to trigger its error handler
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6845
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.3, 2.12.2, 2.13.0
>
>
> This route
> {code}
>                 errorHandler(deadLetterChannel("mock:dead"));
>                 from("direct:start")
>                     .recipientList().constant("direct:foo")
>                     .to("mock:result");
>                 from("direct:foo")
>                     .errorHandler(noErrorHandler())
>                     .to("mock:foo")
>                     .process(new Processor() {
>                         @Override
>                         public void process(Exchange exchange) throws Exception {
>                             throw new IllegalArgumentException("Forced");
>                         }
>                     });
> {code}
> So in the 2nd route we disabled error handling by using the no error handler. Instead we would like the error handler from the caller route (the 1st) which will fallback and use the context scoped dead letter channel to handle the exception.



--
This message was sent by Atlassian JIRA
(v6.1#6144)