[jira] Commented: (CAMEL-1580) Move stop() and proceed() DSL to InterceptorDefinition so its not listed in big list of DSL methods

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51481#action_51481 ] 

Claus Ibsen commented on CAMEL-1580:
------------------------------------

In Java DSL the method must be right after intercept() as we have defined the builder method on InterceptDefinition.

> Move stop() and proceed() DSL to InterceptorDefinition so its not listed in big list of DSL methods
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1580
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1580
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-core
>    Affects Versions: 2.0-M1
>            Reporter: Claus Ibsen
>            Priority: Minor
>
> We can move {{stop}} and {{proceed}} to the interceptors that support them.
> This reduces the confusing of them in the general DSL list.
> And we can let spring DSL use an attribute to define stop instead of proceed.
> Kinda like the interceptSendToEndpoint that has an attribute to skip sending to original endpoint.
> The problem is to find a good name for a DSL that indicates that we *do not* proceed
> {code}
> intercept().notProceed().to("mock:intercepted");
> {code}
> And in Spring DSL
> {code:xml}
> <intercept proceed="false">
>   <to uri="mock:intercepted"/>
> </intercept>
> {code}
> Then we do not have: stop, proceed and skip in the DSL anymore, that end users can insert at random positions in the DSL where they have no use.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.