If I understand Guillaume Nodet's blog announcing ServiceMix Kernel
correctly, the Kernel plus Camel will provide both (a) and (b),
without the rest of ServiceMix. I am trying to understand what can be
done with Camel that leaves others free to put Camel routes in the
container of their choice.
Gary Struthers
On Nov 24, 2008, at 9:56 PM, [EMAIL PROTECTED] wrote:
On 20/11/2008, Drone42 <[EMAIL PROTECTED]> wrote:
Have I understood it correctly;
- A CamelContext runs as one application.
- A given instance is thus local.
- If I want a route in a distributed network, then I can use for
example
ServiceMix to integrate Camel instances into a system managing the
complete
flow
Both ServiceMix and Camel have an in Vm model of endpoints & routes.
How you connect multiple VMs together is essentially the same for both
- use endpoints to do the remoting/communication for you - whether it
be file, jms, http, ws or whatever.
The decision of whether to use just camel or servicemix + camel is
more a case of
(a) do you want support for JBI and / or OSGi components?
(b) do you want a container / server to host your routes (with hot
redeploy etc)
If the answer to either of those is yes, use servicemix. Otherwise
just embed camel in your app
--
View this message in context:
http://www.nabble.com/A-Camel-route-in-a-distributed-network-tp20600769s22882p20600769.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
