[
https://issues.apache.org/jira/browse/CAMEL-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181106#comment-13181106
]
Claus Ibsen commented on CAMEL-4807:
------------------------------------
Yeah. I suggest thought to possible add a note about this for the Camel 3.0
roadmap page.
http://camel.apache.org/camel-30-roadmap.html
Then we can see what the improved routing engine can do for us in this regard.
> intercept() doesn't store intercepted endpoint in
> Exchange.INTERCEPTED_ENDPOINT
> -------------------------------------------------------------------------------
>
> Key: CAMEL-4807
> URL: https://issues.apache.org/jira/browse/CAMEL-4807
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.8.3
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Priority: Minor
> Labels: interceptors
> Fix For: 2.10
>
>
> The intercept() DSL doesn't seem to store the intercepted endpoint (if the
> original intended destination at that point is an endpoint) in the
> Exchange.INTERCEPTED_ENDPOINT property.
> This could be useful if you want to build generic interceptor logic which has
> the capability of taking decisions based on if the next processor is a
> specific endpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
