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/04/07 12:07:08 UTC
[jira] Created: (CAMEL-2623) SEDA/VM - Add support for chained
endpoints when using request/reply in async fashion
SEDA/VM - Add support for chained endpoints when using request/reply in async fashion
-------------------------------------------------------------------------------------
Key: CAMEL-2623
URL: https://issues.apache.org/activemq/browse/CAMEL-2623
Project: Apache Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.4.0
Currently SEDA/VM only supports sending request/reply messages between 2 endpoints A -> B in a request/reply style.
If you have 3+ or more then it gets much more complex and its currently not support in Camel. eg A -> B -> C -> D etc.
In this situation we have to deal with
- different timeouts
- ordering of notification of timeout / done to bubble up the chain
This requires API changes in UnitOfWork and improvements in SEDA component to cater for this logic.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2623) SEDA/VM - Add support for chained
endpoints when using request/reply in async fashion
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58792#action_58792 ]
Claus Ibsen commented on CAMEL-2623:
------------------------------------
trunk: 933163.
Preparing for some rework to support this
> SEDA/VM - Add support for chained endpoints when using request/reply in async fashion
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-2623
> URL: https://issues.apache.org/activemq/browse/CAMEL-2623
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
>
> Currently SEDA/VM only supports sending request/reply messages between 2 endpoints A -> B in a request/reply style.
> If you have 3+ or more then it gets much more complex and its currently not support in Camel. eg A -> B -> C -> D etc.
> In this situation we have to deal with
> - different timeouts
> - ordering of notification of timeout / done to bubble up the chain
> This requires API changes in UnitOfWork and improvements in SEDA component to cater for this logic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (CAMEL-2623) SEDA/VM - Add support for chained
endpoints when using request/reply in async fashion
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2623.
--------------------------------
Fix Version/s: 2.3.0
(was: 2.4.0)
Resolution: Fixed
trunk: 933214.
> SEDA/VM - Add support for chained endpoints when using request/reply in async fashion
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-2623
> URL: https://issues.apache.org/activemq/browse/CAMEL-2623
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.3.0
>
>
> Currently SEDA/VM only supports sending request/reply messages between 2 endpoints A -> B in a request/reply style.
> If you have 3+ or more then it gets much more complex and its currently not support in Camel. eg A -> B -> C -> D etc.
> In this situation we have to deal with
> - different timeouts
> - ordering of notification of timeout / done to bubble up the chain
> This requires API changes in UnitOfWork and improvements in SEDA component to cater for this logic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira