Hi guys, My camel routes basically represent business services. I started with 2 routes and now I have over 50. The project is a spring MVC/maven deployed in a Tomcat server. The routes are accessible via ActiveMQ using JMS. Everything works fine except when it comes to updating or fixing a bug in one route which results in a full test and deployment cycle for the entire project. This is not desirable as many systems are now relying on these routes/services to get data.
Now I am in the process of splitting these routes into OSGi bundles and deploy them into Apache karaf container. I have one (big) question regarding the best practices and hope you guys can help me with: - Should I still be using JMS (via ActiveMQ) to access routes from external projects? are there alternative and more efficient way to access OSGi services from non-OSGi applications? -- View this message in context: http://camel.465427.n5.nabble.com/Why-using-camel-routes-via-activemq-in-Apache-karaf-tp5774011.html Sent from the Camel - Users mailing list archive at Nabble.com.
