Claus,
You're absolutely right, that's another viable option -- here's the
thread [1] that discusses Teracotta support.
Regards,
Gert
[1]
http://www.nabble.com/Working-Terracotta-Component---Clustered-Queues-in-Camel-td15941549s22882.html
Claus Ibsen wrote:
Hi
And hasn't one of the teracotta guys created a integration with camel so you
can use their cluster software out-of-the-box?
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Gert Vanthienen [mailto:[EMAIL PROTECTED]
Sent: 22. maj 2008 12:04
To: [email protected]
Subject: Re: Camel Request Reply Networked Broker
Carloc,
Camel is just a framework/API for enterprise integration -- it doesn't
support the CamelContexts themselves to be distributed. However, you
can use Camel on top of ActiveMQ or ServiceMix and both of them do
support distributed deployment. This way, you can just have the
CamelContext interact with the local ActiveMQ/ServiceMix instance using
JMS/JBI messaging and they will take care of distributed messaging for
you. Have a look at http://activemq.apache.org/clustering.html or
http://servicemix.apache.org/clustering.html for more information...
Gert
carloc wrote:
Hi,
To Add, Is it possible for Camel Contexts TO Be Distributed?
One camel context in the branch server and one camel context in the central
server that are aware of each other.
Sorry I'm a new user
Thanks
carloc wrote:
Hi,
Thanks For THe Reply....
I'd have to implement the request/reply again but this time it would be on
a networked broker.
How do I do this.
I have a central server and then a branch server.
I have brokers setup on each.
I am doing a request on the branch side. I am requesting on the broker in
my branch I want it to do store and forward to the broker which is on my
central server.
Will it be transparent to me? Or do I still have to configure something.
Thanks