camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-6845) Using recipient list to a route that has no error handler should allow caller route to trigger its error handler
Date Thu, 10 Oct 2013 08:28:45 GMT

     [ 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)

Mime
View raw message