Re: Camel Container Deployment - Best Practice

[alexey-s <al...@mail.ru>]

I use a bunch of Apache Karaf and Apache Camel.
At the beginning of the road I used OSGi Blueprint.
Over time, the Blueprint gave up and switched to Dynamic Services.

Spring DS - a type of OSGi Blueprint. It was quite a compelling reason
authors
abandon basic Spring DS in OSGi. This is the main reason for the refusal of
Spring.

Daylight OSGi DS due order to start and stop Camel Contexts, depending on
the OSGi Services.
When using Blueprint, running processes are not stopped.
The process of trying to interact with the modified service hidden behind
Blueprint Proxy. It is not always correct.
OSGi DS stops Camel service, change the basic services and start new
processes.
This is convenient for the loss and restoration of communication between
servers.

As the system works with a database made the choice to MyBatis Guice.
Do not fall for lack of JPA Transaction Manager in a JBoss AS.
Do not work properly annotations transaction management.
Camel (Spring) Transaction very hard to maintain.

The main branch of the project MyBatys implemented the idea of ​​the dynamic
release
resources. This gave a dynamic replacement OSGi Bundles without the need for
stop the server Apache Karaf.

The main branch of the project implemented support for MyBatis Guice
Transaction Manager. Annotations and Camel (Spring) Transaction working
properly.




--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Container-Deployment-Best-Practice-tp5772655p5772735.html
Sent from the Camel - Users mailing list archive at Nabble.com.