For testing, you have some frameworks with OSGI too: * You can use Spring for unit testing (it will replace blueprint as test context) * You can use pax-exam (maybe with karaf-pax-exam-container) for integration testing (all your stack, as you would do with spring/tomcat)
2014-07-22 13:59 GMT+02:00 Charlie Mordant <cmorda...@gmail.com>: > I think it is also a question of modularity/concern. > > The major subject of Camel is to make routes between services (EIPs). > So everytime you deploy a new service (and so modify your routes) you'll > have to stop and restart them. > > Now, if you have mutliple routes on the same Vm and use Spring, a major > part of your IS will be unavailable (and you'll maybe have some issues with > 'on process' exchanges). > If you use OSGI, the only bundles that must be refreshed is the one that > contains your modified routes, reducing the issues/outage due to hot swap, > conncurrent versions support, live configuration swap... > > Concerning fuse, I think it uses Karaf under the hood too.. > > Regards, > > > > > 2014-07-22 12:02 GMT+02:00 akoufoudakis <akoufouda...@gmail.com>: > > That is what official Red Hat Fuse ESB Enterprise documentations says: >> "When trying to decide between the blueprint and Spring dependency >> injection >> frameworks, bear in mind that blueprint offers one major advantage over >> Spring: when new dependencies are introduced in blueprint through XML >> schema >> namespaces, blueprint has the capability to resolve these dependencies >> automatically at run time. By contrast, when packaging your project as an >> OSGi bundle, Spring requires you to add new dependencies explicitly to the >> maven-bundle-plugin configuration." >> ( >> https://access.redhat.com/documentation/en-US/Fuse_ESB_Enterprise/7.0/html/Getting_Started/ch01s04s02.html >> ). >> >> As for the fuse/karaf, I might be wrong. But looking at the examples, it >> seems that Fabric uses Karaf behind the scenes. I might be wrong about it. >> So, please, double check. >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/What-would-be-the-benefits-of-running-Camle-on-osgi-tp5754201p5754202.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > > > -- > Charlie Mordant > > Full OSGI/EE stack made with Karaf: > https://github.com/OsgiliathEnterprise/net.osgiliath.parent > -- Charlie Mordant Full OSGI/EE stack made with Karaf: https://github.com/OsgiliathEnterprise/net.osgiliath.parent
