Charles Moulliard wrote:
On the wiki page of camel concerning vm, they suggests that vml:// can
be used across different JVM
Here is the text :
"This component differs from the SEDA component in that VM supports
communication across CamelContext instances, so you can use this
mechanism to communicate across web applications, provided that the
camel-core.jar is on the system/boot classpath.
This component is an extension to the SEDA component."
It just across the web applications, and the application container still
a single JVM.
BTW, SEDA component can't be used across the JVMs.
Kind regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Fri, Feb 26, 2010 at 1:28 PM, Willem Jiang <[email protected]> wrote:
Hi,
Charles Moulliard wrote:
Based on James feedback, I have adapted the categories. I will create
a wiki page on camel wiki to show the different options
1. Loadbalancing
loadbalance() : http://camel.apache.org/load-balancer.html
2. Clustering
2.1. Same JVM & CamelContext
seda:// : http://camel.apache.org/seda.html or direct://
and threads()
jms:// or activemq:// and threads()
2.2 Different JVM & CamelContext
2.2.1. Suitable for solutions running in standalone mode or deployed
in Web Application Server (different WAR/EAR)
vm:// : http://camel.apache.org/vm.html or jms:// - activemq://
After checking the wiki page and vm component code, I'm sure vm component
can't be used across the JVM.
I think we need to change this part.
2.2.2. Between different instances of OSGI servers (SMX4)
nmr:// : http://camel.apache.org/nmr.html or jms:// - activemq://
2.2.3. If message persistence is required
jms:// - activemq://
4. Cloudcomputing
4.1 Cassandra
It could be interesting to create a Cassandra endpoint to allow to
consume
info/camel messages from Cassandra DB (NOSQL database) or to push there
camel message (using id + binary stream). It might also make an
interesting
aggregator implementation since its also distributed & can support
multi-master
4.2 camel-terracotta
Extends the SEDA component
Kind regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
