camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Moulliard (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5368) component direct:// does not offer cross bundle communication like nmr:// or vm://
Date Wed, 20 Jun 2012 08:26:43 GMT

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

Charles Moulliard commented on CAMEL-5368:
------------------------------------------

The component "camel-osgi" seems really interesting as it allows cross bundles communication
"endpoints of Camel Contexts are registered in the OSGI Registry". The question is : "Does
it support TX propagation with or without Spring ?" 

                
> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0
>
>


--
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