You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Charles Moulliard (JIRA)" <ji...@apache.org> on 2012/06/14 14:31:42 UTC
[jira] [Created] (CAMEL-5368) component direct:// does not offer
cross bundle communication like nmr:// or vm://
Charles Moulliard created CAMEL-5368:
----------------------------------------
Summary: 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
[jira] [Commented] (CAMEL-5368) component direct:// does not offer
cross bundle communication like nmr:// or vm://
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295498#comment-13295498 ]
Claus Ibsen commented on CAMEL-5368:
------------------------------------
The direct component is purely for direct message exchanges within the *same* CamelContext in the same classloader. Its *not* intended for cross CamelContext communication or for OSGi environments.
For OSGi environments you should look for other Camel components. For example there is the nmr, bean (invoking beans referenced from osgi service registry), and there is work in progress from the community on a new camel osgi component. I suggest to take a look at that
http://camel.465427.n5.nabble.com/Camel-OSGi-services-component-tp5713354.html
This component seems really compelling. So take a look at that, as we need more feedback on that, before taking that into the Camel distribution.
> 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
> 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
[jira] [Commented] (CAMEL-5368) component direct:// does not offer
cross bundle communication like nmr:// or vm://
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CAMEL-5368) component direct:// does not offer
cross bundle communication like nmr:// or vm://
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5368.
--------------------------------
Resolution: Not A Problem
Fix Version/s: 2.10.0
Assignee: Claus Ibsen
> 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
[jira] [Commented] (CAMEL-5368) component direct:// does not offer
cross bundle communication like nmr:// or vm://
Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
[ 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