You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/08/06 03:36:51 UTC

[jira] Resolved: (CAMEL-2971) Option to control if async processing should be used or not on endpoint

     [ https://issues.apache.org/activemq/browse/CAMEL-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2971.
--------------------------------

    Resolution: Fixed

See wiki page
https://cwiki.apache.org/confluence/display/CAMEL/Asynchronous+Routing+Engine

> Option to control if async processing should be used or not on endpoint
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-2971
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2971
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.5.0
>
>
> If ordering really matters it should be possible to configure the endpoint to dictate synchronous routing only.
> {code}
> from("activrmq:xxx")
>    .to("cxf:bla")
>    .to("activemq:yyy");
> {code}
> Now suppose ordering is important, but as cxf is async now, it can cause the ordering to break. And therefore you should be able to configure CXF to be sync only
> {code}
> from("activrmq:xxx")
>    .to("cxf:bla?synchronous=true")
>    .to("activemq:yyy");
> {code}
> But finding a good name for the option can be tricky. Should it be synchronous or asynchronous ?
> This should be implemented in a generic fashion. By using a delegate processor which is either async or sync. 

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