Ah I missed that. Thanks. On Wed, Jul 18, 2012 at 3:50 PM, thomas barker <thomas.p.bar...@gmail.com> wrote: > I guess it does: http://camel.apache.org/hazelcast-component.html > > To be honest there are many options to get this to work, so I would use > whatever you know best and are most comfortable with. If you don't want to > rock the boat, most people here probably have more experience with camel's > jms support than any other option mentioned. > > > On Wed, Jul 18, 2012 at 10:45 AM, Sam (Stephen Samuel) > <samspad...@gmail.com> wrote: >> >> I'll stick with JMS then, didn't know if Camel had some kind of >> Hazelcast type thing. >> >> On Wed, Jul 18, 2012 at 3:39 PM, thomas barker >> <thomas.p.bar...@gmail.com> wrote: >> > If you use JMS use activemq if you can... the http / servlet / jetty >> > components are lightweight options as well. >> > >> > On Wed, Jul 18, 2012 at 10:36 AM, Charles <cw94...@yahoo.com> wrote: >> > >> >> 1.) Use JMS >> >> 2.) Use CXF (web services) >> >> >> >> I've done #1, it's probably easier. >> >> >> >> >> >> ----- Original Message ----- >> >> From: Sam (Stephen Samuel) <samspad...@gmail.com> >> >> To: users@camel.apache.org >> >> Cc: >> >> Sent: Wednesday, July 18, 2012 10:28 AM >> >> Subject: Camel Routes across JVMs >> >> >> >> Hi, >> >> >> >> What's the best practice for having routes communicate across VMs? >> >> Specifically speaking I want an application to send messages to >> >> another on a separate server and the 2nd server to process those >> >> messages in its own camel route. >> >> >> >> >> >> >> >> -- >> -Sam > >
-- -Sam
