Hi Gabriel, I confirm what Jean Baptiste told you.
NMR is for INTER bundles communications or ActiveMq. NMR name will change in the future Seda, Direct is for INTRA bundle communication Remark : VM has been created for deployment in Web Application Servers where we have a tree classloader used in one JVM Regards, Charles Moulliard Sr. Principal Solution Architect - FuseSource Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard On Fri, May 13, 2011 at 9:09 AM, Gabriel D'Halluin <[email protected]> wrote: > Thank you for your response, > I didn't know the VM component communication has to be between > elements of the same classloader, which makes the fact it is not made > for a OSGi purpose very clear. > Regards, Gabriel. > > 2011/5/13 Jean-Baptiste Onofré <[email protected]>: >> Hi Gabriel, >> >> Between two OSGi bundles, you can use: >> - pure OSGi services usage. This OSGi usage could be set in a blueprint >> descriptor, the same hosting Camel routes. >> - ServiceMix NMR. It's different from the vm: component. NMR provides to you >> a rich messaging and endpoint API, including audit, security, etc. >> >> Camel VM component is an extension of the SEDA component, so the usage is a >> bit different as asynchronous and allow communication in the same >> JVM/classloader. It's not really directly applicable using Camel routes >> splitted into differents bundles. >> >> Regards >> JB >> >> On 05/13/2011 07:12 AM, Gabriel.DHalluin wrote: >>> >>> Hello everyone, >>> >>> I am migrating a existing server to an OSGi platform, using karaf, camel, >>> and spring. >>> I need to make two OSGi bundles communicate each other, and we previously >>> used the camel vm component to make this exchange. After a little bit of >>> research, I've seen the servicemix NMR is commonly used, but there is also >>> some references to the vm component. So the question is can i still used >>> the >>> camel-vm to make my bundles communicate? I've seen >>> http://fusesource.com/forums/thread.jspa?messageID=5987 , >>> >>> http://trenaman.blogspot.com/2010/08/easy-useful-nmr-monsieur-nodet-vous.html >>> , but on none of this posts the question is clearly answered. Then i saw: >>> >>> The vm:// component of camel plays the same role as NMR to interconnect >>> camel routes deployed in different bundles. So the added value of NMR in >>> this case is very poor/limited. I don't think that we need anymore NMR in >>> the future except if we have features present in NMR that camel cannot >>> implement. >>> >>> in >>> >>> http://servicemix.396122.n5.nabble.com/DISCUSS-ServiceMix-future-td3212177i40.html >>> and then >>> >>> The VM wasn't really meant for osgi. It was for sharing messages >>> between WAR files deployed in Apache Tomcat etc. >>> In OSGi there are OSGi services and/or the NMR component for sharing >>> messages between bundles. >>> >>> in >>> >>> http://camel.465427.n5.nabble.com/Question-on-VM-Endpoint-multipleConsumers-and-OSGi-td3284450.html#a3286168 >>> >>> So I'm getting a bit confused here, is it possible/advised to use the >>> camel-vm component in a OSGi framework, or should I use NMR? Are there any >>> advantages/disadvantages for either of them? >>> I hope i didn't miss any obvious answer. >>> >>> Thank you, >>> Regards, >>> Gabriel >>> >>> -- >>> View this message in context: >>> http://camel.465427.n5.nabble.com/Camel-vm-and-nmr-in-a-OSGi-framework-tp4392206p4392206.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >> >
