Hi there, I'd say yes: you should pursue the use of Camel routes, deployed using OSGi bundles, and with appropriate use of ActiveMQ as necessary to give you a reliable asynchronous messaging that really forms the heart of any ESB.
I've written about the use of JBI and NMR on my blog http://trenaman.blogspot.com - just search the blog for 'JBI' and 'NMR' and you'll get the articles. For me, the recent work to abstract the NMR away from JBI into a core, high-performance, asychronous mechanism for inter-bundle/inter-route communication is compelling and worthy of investigation. In that context, use of the JBI container becomes a peripheral part of the integration landscape as opposed to a central tenet of the architecture. Hope that helps! Go with ServiceMix: you're going to love it. /Ade ----- Original Message ----- From: gmui [mailto:[email protected]] Sent: Wednesday, September 15, 2010 10:28 AM To: [email protected] <[email protected]> Subject: Re: JBI or just OSGi? Thanks for the fast replies. It helps to answer my question as to whether this has an active community :) I guess my question is if I'm looking for a non-JBI based ESB but want to use the rest of the ServiceMix technology stack, should I be looking to deploy Camel routes and components as OSGi bundles onto the Felix Karaf container? Besides the NMR, do I lose a lot of other functionality that ServiceMix provides? It seems that a lot of the servicemix components like File, JMS, etc are also binding components in Camel already. -- View this message in context: http://servicemix.396122.n5.nabble.com/JBI-or-just-OSGi-tp2840633p2840723.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
