Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <25018259.post@talk.nabble.com>
Date: Mon, 17 Aug 2009 21:25:01 -0700 (PDT)
From: snowbug <laji.inbox@gmail.com>
To: users@camel.apache.org
Subject: Re: Accessing CamelContext from different applications
In-Reply-To: <4A89FB63.2080604@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <24957829.post@talk.nabble.com> <4A85046E.6010507@gmail.com>
 <25013084.post@talk.nabble.com> <4A89FB63.2080604@gmail.com>


willem.jiang wrote:
> 
> Hi,
> 
> Yes , you assumption is correct.
> If you want to directly talk to camel context in the same JVM, you could 
> choice direct,  seda component. But if you want to do that across the 
> JVMs, you have to other components :)
> 
> Willem
> 

Thank you for the confirmation. I am quite new to Camel so please allow me
to get more clarification on your "other components" comments. My
understanding to that is people would need to create JMS (or HTTP, or other)
component in the Camel app to allow other apps to send messages to it, and
the same time create application specific components in the Camel app to
send messages from the Camel app to other apps?

Thanks for you help,

Alan

-- 
View this message in context: http://www.nabble.com/Accessing-CamelContext-from-different-applications-tp24957829p25018259.html
Sent from the Camel - Users mailing list archive at Nabble.com.