camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Kripalani (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4807) intercept() doesn't store intercepted endpoint in Exchange.INTERCEPTED_ENDPOINT
Date Thu, 05 Jan 2012 16:23:39 GMT


Raul Kripalani commented on CAMEL-4807:

Claus, I see. Not sure if the Message History EIP would fit this scenario, since by definition
it only injects the processor/node ID *after* the message has been processed, whereas my idea
entails storing where the message is going next (kind of like an addressing header - à la
WS-Addressing). But I get your point. Shall we change the resolution to "Not a problem"?
> intercept() doesn't store intercepted endpoint in Exchange.INTERCEPTED_ENDPOINT
> -------------------------------------------------------------------------------
>                 Key: CAMEL-4807
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message