[
https://issues.apache.org/jira/browse/CAMEL-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180257#comment-13180257
]
Claus Ibsen commented on CAMEL-4807:
------------------------------------
Raul
I do not think this is the way to go currently in the 2.x architecture.
When we overhaul and make the internal routing engine more dynamic, we can
revisit the Message History EIP pattern, to have better details. As the logic
is also related to the Tracer etc.
With the overhauled routing engine we have a better spot to implement and
control this kind of logic.
> 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
>
> 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
