camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5368) component direct:// does not offer cross bundle communication like nmr:// or vm://
Date Thu, 14 Jun 2012 12:35:42 GMT

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

Guillaume Nodet commented on CAMEL-5368:
----------------------------------------

AFAIK, the need is to have cross camel context synchronous routes, so that transactions can
be propagated.
It may be easier to reuse the existing vm component, but add a synchronous flag.
                
> component direct:// does not offer cross bundle communication like nmr:// or vm://
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-5368
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5368
>             Project: Camel
>          Issue Type: Improvement
>         Environment: Component direct:// does not offer cross bundle communication (or
between 2 different camel spring application context) like nmr:// or vm://
> This is a limitation as we cannot create Tx routes in this case as until now we do not
support async Tx which is required for vm:// or nmr://
>            Reporter: Charles Moulliard
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message