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-4809) interceptSendToEndpoint with predicate and skip
Date Wed, 04 Jan 2012 16:29:39 GMT


Raul Kripalani commented on CAMEL-4809:

Thanks Claus. I didn't want to take the step of changing the fluent builder just in case users
were relying on the returned ChoiceDefinition. But it makes more sense this way, definitely.
I've attached a new version of the patch. This time with checkstyle passed ;)
> interceptSendToEndpoint with predicate and skip
> -----------------------------------------------
>                 Key: CAMEL-4809
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-spring
>            Reporter: Raul Kripalani
>            Assignee: Claus Ibsen
>         Attachments: interceptSendToEndpointConditionalSkip.diff, interceptSendToEndpointConditionalSkip_v2.diff,
> The <when> clause in the interceptors behave like filters. This is okay with intercept
and interceptFrom, where the only possible route manipulation is <stop />, which is
expressed inside the routing block.
> However, with interceptSendToEndpoint there is one edge case that could cause ambiguity.
When skipSendToEndpoint=true, along with a <when> clause, the user might expect that
the skipping will only occur if the condition is met. However, it occurs always. The <when
/> only determines whether the routing logic contained inside the body of the intercept
block will occur or not.
> I propose to add a new attribute onlySkipWhenConditionMet, so that when this is true,
the <when> clause will be evaluated to determine if the originally intended endpoint
is actually skipped or not.

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