[
https://issues.apache.org/activemq/browse/CAMEL-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52528#action_52528
]
Claus Ibsen commented on CAMEL-1260:
------------------------------------
See CAMEL-1750 where you can provide a pluggable poll strategy.
That allows you to decide what to do. However its not supported as a DSL like
this proposal.
I wonder if we should use URI matching like the interceptFromEndpoint that
supports wildcard and regex
Then you can do
{code}
from("error:file*").to("bean:handleFilePollError");
{code}
And to do all scheduled polling consumer just
{code}
from("error:*").to("bean:handleFilePollError");
{code}
> should we use endpoints for errors thrown by things like
> ScheduledPollConsumer - so folks can choose to log them, route them, or just
> ignore them
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1260
> URL: https://issues.apache.org/activemq/browse/CAMEL-1260
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Assignee: Jonathan Anstey
> Fix For: 2.1.0
>
>
> I wonder if a more flexible fix to CAMEL-501 is to send errors to a
> configured endpoint URI - then folks can choose to route them wherever they
> like (to a log, ignore them, throw them on shutdown etc).
> e.g. rather than log the exception, send the exception as a message to some
> error endpoint like error:ScheduledPollConsumer. Folks could then
> * override the URI to send errors to in the ScheduledPollConsumer
> * create a route
> {code}
> from("error:ScheduledPollConsumer").to("log:Foo");
> {code}
> * the default behaviour for any error endpoint could maybe be - if there are
> no consumers defined, we log to the error console?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
