You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Drone42 <ge...@logica.com> on 2008/11/20 14:09:30 UTC
A Camel route in a distributed network
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
--
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.
Re: A Camel route in a distributed network
Posted by James Strachan <ja...@gmail.com>.
2008/11/25 Drone42 <ge...@logica.com>:
>
> Well, couldnt I use a Camel SU instance (A.1) inside a SM instance (A) to
> publishe a WebService and another Camel SU instance (B.1) inside a SM
> instance (B) to consume the service? In this case the integration between
> the two SM instances is actualy through Camel (with Web Service in between).
>
> As I'm a fan of typed interfaces between components in a distributed network
> this is anyway how I would do it, i.e. make sure there is a proper service
> definition in between.
BTW if you were not using ServiceMix you could achieve something
similar - using typed interfaces between components - but using any
transport/protocol
http://activemq.apache.org/camel/components.html
using Spring Remoting
http://activemq.apache.org/camel/spring-remoting.html
or
http://activemq.apache.org/camel/pojo-producing.html
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: A Camel route in a distributed network
Posted by James Strachan <ja...@gmail.com>.
2008/11/25 Drone42 <ge...@logica.com>:
>
> Well, couldnt I use a Camel SU instance (A.1) inside a SM instance (A) to
> publishe a WebService and another Camel SU instance (B.1) inside a SM
> instance (B) to consume the service? In this case the integration between
> the two SM instances is actualy through Camel (with Web Service in between).
Absolutely. You can use any mechanism to connect routes together using
any of these technologies...
http://activemq.apache.org/camel/components.html
pick which ever flavour takes your fancy and most suits your use cases.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: A Camel route in a distributed network
Posted by Drone42 <ge...@logica.com>.
Well, couldnt I use a Camel SU instance (A.1) inside a SM instance (A) to
publishe a WebService and another Camel SU instance (B.1) inside a SM
instance (B) to consume the service? In this case the integration between
the two SM instances is actualy through Camel (with Web Service in between).
As I'm a fan of typed interfaces between components in a distributed network
this is anyway how I would do it, i.e. make sure there is a proper service
definition in between.
willem.jiang wrote:
>
> Hi,
>
> Mick Knutson wrote:
>> But each SM component can use camel to route internally, then rely on SM
>> to
>> route to the other SM component right?
> Yes
>>
>> But it would not be a pure camel routing, but you could still distribute
>> different services.
> Yes
>>
>
> Willem
>
>>
>> On Thu, Nov 20, 2008 at 8:48 AM, Willem Jiang
>> <wi...@gmail.com>wrote:
>>
>>> You can get the 2 different SM engines connected by using the SM's
>>> components not the camel components.
>>>
>>> Willem
>>>
>>> Mick Knutson wrote:
>>>> If you have 2 different SM engines, you could have camelAppA running on
>>> 1,
>>>> then camelAppB running on another one. Could you not at that point
>>>> route
>>>> from camelAppA to camelAppB?
>>>>
>>>> On Thu, Nov 20, 2008 at 8:28 AM, Willem Jiang <willem.jiang@gmail.com
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Please see my comments in the mail.
>>>>>
>>>>> Drone42 wrote:
>>>>>> Have I understood it correctly;
>>>>>>
>>>>>> - A CamelContext runs as one application.
>>>>> Yes
>>>>>> - A given instance is thus local.
>>>>> Yes
>>>>>> - 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
>>>>> You could use camel-activmq, camel-cxf even camel-file components to
>>>>> build up the distributed network endpoint and using the camel DLS to
>>>>> build the route rule.
>>>>> AFAIK ServiceMix's components are stay in the same JVM.
>>>>>
>>>>> Willem
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/A-Camel-route-in-a-distributed-network-tp20600769s22882p20677442.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: A Camel route in a distributed network
Posted by Willem Jiang <wi...@gmail.com>.
Hi,
Mick Knutson wrote:
> But each SM component can use camel to route internally, then rely on SM to
> route to the other SM component right?
Yes
>
> But it would not be a pure camel routing, but you could still distribute
> different services.
Yes
>
Willem
>
> On Thu, Nov 20, 2008 at 8:48 AM, Willem Jiang <wi...@gmail.com>wrote:
>
>> You can get the 2 different SM engines connected by using the SM's
>> components not the camel components.
>>
>> Willem
>>
>> Mick Knutson wrote:
>>> If you have 2 different SM engines, you could have camelAppA running on
>> 1,
>>> then camelAppB running on another one. Could you not at that point route
>>> from camelAppA to camelAppB?
>>>
>>> On Thu, Nov 20, 2008 at 8:28 AM, Willem Jiang <willem.jiang@gmail.com
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> Please see my comments in the mail.
>>>>
>>>> Drone42 wrote:
>>>>> Have I understood it correctly;
>>>>>
>>>>> - A CamelContext runs as one application.
>>>> Yes
>>>>> - A given instance is thus local.
>>>> Yes
>>>>> - 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
>>>> You could use camel-activmq, camel-cxf even camel-file components to
>>>> build up the distributed network endpoint and using the camel DLS to
>>>> build the route rule.
>>>> AFAIK ServiceMix's components are stay in the same JVM.
>>>>
>>>> Willem
>>>>
>>>>
>>>>
>>>
>>
>
>
Re: A Camel route in a distributed network
Posted by Mick Knutson <mk...@baselogic.com>.
But each SM component can use camel to route internally, then rely on SM to
route to the other SM component right?
But it would not be a pure camel routing, but you could still distribute
different services.
On Thu, Nov 20, 2008 at 8:48 AM, Willem Jiang <wi...@gmail.com>wrote:
> You can get the 2 different SM engines connected by using the SM's
> components not the camel components.
>
> Willem
>
> Mick Knutson wrote:
> > If you have 2 different SM engines, you could have camelAppA running on
> 1,
> > then camelAppB running on another one. Could you not at that point route
> > from camelAppA to camelAppB?
> >
> > On Thu, Nov 20, 2008 at 8:28 AM, Willem Jiang <willem.jiang@gmail.com
> >wrote:
> >
> >> Hi
> >>
> >> Please see my comments in the mail.
> >>
> >> Drone42 wrote:
> >>> Have I understood it correctly;
> >>>
> >>> - A CamelContext runs as one application.
> >> Yes
> >>> - A given instance is thus local.
> >> Yes
> >>> - 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
> >> You could use camel-activmq, camel-cxf even camel-file components to
> >> build up the distributed network endpoint and using the camel DLS to
> >> build the route rule.
> >> AFAIK ServiceMix's components are stay in the same JVM.
> >>
> >> Willem
> >>
> >>
> >>
> >
> >
>
>
--
Thank You…
Mick Knutson
BASE Logic, inc.
(415) 685-4233
Website: http://baselogic.com
Blog: http://baselogic.com/blog
BLiNC Magazine: http://blincmagazine.com
Linked IN: http://linkedin.com/in/mickknutson
DJ Mick: http://djmick.com
MySpace: http://myspace.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
coming soon: (866-BLiNC-411: (254-6241-1)
---
Re: A Camel route in a distributed network
Posted by Willem Jiang <wi...@gmail.com>.
You can get the 2 different SM engines connected by using the SM's
components not the camel components.
Willem
Mick Knutson wrote:
> If you have 2 different SM engines, you could have camelAppA running on 1,
> then camelAppB running on another one. Could you not at that point route
> from camelAppA to camelAppB?
>
> On Thu, Nov 20, 2008 at 8:28 AM, Willem Jiang <wi...@gmail.com>wrote:
>
>> Hi
>>
>> Please see my comments in the mail.
>>
>> Drone42 wrote:
>>> Have I understood it correctly;
>>>
>>> - A CamelContext runs as one application.
>> Yes
>>> - A given instance is thus local.
>> Yes
>>> - 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
>> You could use camel-activmq, camel-cxf even camel-file components to
>> build up the distributed network endpoint and using the camel DLS to
>> build the route rule.
>> AFAIK ServiceMix's components are stay in the same JVM.
>>
>> Willem
>>
>>
>>
>
>
Re: A Camel route in a distributed network
Posted by Mick Knutson <mk...@baselogic.com>.
If you have 2 different SM engines, you could have camelAppA running on 1,
then camelAppB running on another one. Could you not at that point route
from camelAppA to camelAppB?
On Thu, Nov 20, 2008 at 8:28 AM, Willem Jiang <wi...@gmail.com>wrote:
> Hi
>
> Please see my comments in the mail.
>
> Drone42 wrote:
> > Have I understood it correctly;
> >
> > - A CamelContext runs as one application.
> Yes
> > - A given instance is thus local.
> Yes
> > - 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
> You could use camel-activmq, camel-cxf even camel-file components to
> build up the distributed network endpoint and using the camel DLS to
> build the route rule.
> AFAIK ServiceMix's components are stay in the same JVM.
>
> Willem
>
>
>
--
Thank You…
Mick Knutson
BASE Logic, inc.
(415) 685-4233
Website: http://baselogic.com
Blog: http://baselogic.com/blog
BLiNC Magazine: http://blincmagazine.com
Linked IN: http://linkedin.com/in/mickknutson
DJ Mick: http://djmick.com
MySpace: http://myspace.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
coming soon: (866-BLiNC-411: (254-6241-1)
---
Re: A Camel route in a distributed network
Posted by Willem Jiang <wi...@gmail.com>.
Hi
Please see my comments in the mail.
Drone42 wrote:
> Have I understood it correctly;
>
> - A CamelContext runs as one application.
Yes
> - A given instance is thus local.
Yes
> - 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
You could use camel-activmq, camel-cxf even camel-file components to
build up the distributed network endpoint and using the camel DLS to
build the route rule.
AFAIK ServiceMix's components are stay in the same JVM.
Willem
Re: A Camel route in a distributed network
Posted by James Strachan <ja...@gmail.com>.
2008/11/25 Gary Struthers <gs...@berkeley.edu>:
> 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.
Nothing; you can already use whatever container you like for Camel :)
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: A Camel route in a distributed network
Posted by Gary Struthers <gs...@berkeley.edu>.
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, james.strachan@gmail.com wrote:
> On 20/11/2008, Drone42 <ge...@logica.com> 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/
Re: A Camel route in a distributed network
Posted by ja...@gmail.com.
On 20/11/2008, Drone42 <ge...@logica.com> 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/