Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 90526 invoked from network); 18 Aug 2009 04:51:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Aug 2009 04:51:48 -0000 Received: (qmail 77627 invoked by uid 500); 18 Aug 2009 04:52:07 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 77569 invoked by uid 500); 18 Aug 2009 04:52:07 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 77559 invoked by uid 99); 18 Aug 2009 04:52:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2009 04:52:07 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.198.243 as permitted sender) Received: from [209.85.198.243] (HELO rv-out-0708.google.com) (209.85.198.243) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2009 04:51:56 +0000 Received: by rv-out-0708.google.com with SMTP id c5so902737rvf.56 for ; Mon, 17 Aug 2009 21:51:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=yVN8gngBtZyANIz2Jrt5OgvoaCMp6MEoWn5z2Bpglkk=; b=gSdtVqbcwqxOmeuucjxKt8PPVXH3/ThM/t8YOQAHciS348pSXe6H5lYsI3PRaLzHfO WrgnqdsevFHm7uUArlEpRx/Tz04VPYFUEnlBTFGLHFETuQqBEDKVtLt2hal1IyCWyt4r sqCWZ95MnIzGGgcUurrslcrRduCXXPhxlqBF4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=OXniYQI1LOwD1HIunY352Uh+wQriOzQPV6V4uDQHF0b2U1WxJoVl3tbRQdbRTcNtGH NHkDEzyISH+4HUhWb0Q6QYWDvqacX83DAHhJmi+bYYTTQhy9aWxCCBOxaT9/mRNWo+8O l83exPYfRATQGRlQkftSAfvZTGN8bW7joOQeI= Received: by 10.140.127.20 with SMTP id z20mr2596951rvc.186.1250571095466; Mon, 17 Aug 2009 21:51:35 -0700 (PDT) Received: from ?192.168.0.158? ([222.131.242.198]) by mx.google.com with ESMTPS id b39sm24247131rvf.30.2009.08.17.21.51.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 17 Aug 2009 21:51:34 -0700 (PDT) Message-ID: <4A8A334E.9080302@gmail.com> Date: Tue, 18 Aug 2009 12:51:26 +0800 From: Willem Jiang User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: Accessing CamelContext from different applications References: <24957829.post@talk.nabble.com> <4A85046E.6010507@gmail.com> <25013084.post@talk.nabble.com> <4A89FB63.2080604@gmail.com> <25018259.post@talk.nabble.com> In-Reply-To: <25018259.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org snowbug wrote: > > > 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 > Yes, you absolutely right :) Willem