camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From borgel <>
Subject Re: Newbie: How to implement the Message Channel pattern?
Date Wed, 27 Jun 2007 20:02:43 GMT

James.Strachan wrote:
> On 6/27/07, borgel <> wrote:
>>> (...) Can I use Camel to send messages between these applications?
>>Sure! :)
> Great! :)
>>Are the 3 applications in the same JVM; or in separate ones? Also are
>>they deployed as a single unit all the time; or could they come and go
> Same JVM, but this might change. The applications are deployed separatly
> and can come and go individually.
>>The simplest way to deal with communication between applications or
>>services (which may individually be started/stopped, be inside
>>different class loaders or deployed across different JVMs) is often
>>using messaging. Then the applications are completely decoupled across
>>time, location and JVM. e.g. using ActiveMQ queues for example.
>>Another option could be to use disk (file based messaging).
> This is what I tried, using direct connection. I sat up a Consumer in one
> app (app C with employee information) and a Producer in another
> application. From the producer i tried to call the consumer, but here it
> stopped for me, because the Producer accesses a different context than the
> Consumer. The same goes for JMS. For instance:
> CamelContext container = new DefaultCamelContext(); 
> (...)
> JmsEndpoint endpoint = (JmsEndpoint)
> container.getEndpoint("jms:employee");    
> The Consumer which is listening on this endpoint never receives anything
> becuase it's a different context. What is it I am missing? 
> Should each application (war) include Camel or should it be deployed to
> Tomcat in a different way?
>>If you deploy the 3 WARs together, (...) 
> I can, but I would prefer not to. I must be able to start and stop each
> application independently from the others.

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message