Return-Path: Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org Received: (qmail 21907 invoked from network); 22 May 2008 13:47:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 May 2008 13:47:32 -0000 Received: (qmail 52680 invoked by uid 500); 22 May 2008 13:47:33 -0000 Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org Received: (qmail 52664 invoked by uid 500); 22 May 2008 13:47:33 -0000 Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-dev@activemq.apache.org Delivered-To: mailing list camel-dev@activemq.apache.org Received: (qmail 52653 invoked by uid 99); 22 May 2008 13:47:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2008 06:47:33 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com designates 74.125.46.157 as permitted sender) Received: from [74.125.46.157] (HELO yw-out-1718.google.com) (74.125.46.157) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2008 13:46:45 +0000 Received: by yw-out-1718.google.com with SMTP id 6so28291ywa.86 for ; Thu, 22 May 2008 06:47:00 -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:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=lyB6+hd4LF0FPap4AMH5Z3tunpbgJIKB2/fcX2w9+sE=; b=MYmuHaIW8XpIP/NV6940G3aNUq6i9y1MBJxkLI3Pm1XpTIs/ln8ADL/2vbN7YgiX2MrQIwFtpYLfjxkrLIKs0ZL6sfC+8MmtdV1YbIS3NO0jjO5VvKn8zcTayH2NdwhsZWoR+7uwNrED0vLbRp7ZN1LZ4FBWPnOB6rtSvxtgKOQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SSAl92UcMKe479dK0re1d5PHq1ied9PyHJzBPHfcO5ajfyTKsiXx2k7/C3XR45BxYN+VMaJIyY79w56vxPjbRhsGbm0d3CnWzNvW3j1BBPL1IP2Q+qatovKn2ojimBpcm33Ayf6ZKL7VX0FVyGlkG43udpfrwvWhLZb+p36A4sA= Received: by 10.150.69.41 with SMTP id r41mr245373yba.127.1211464020873; Thu, 22 May 2008 06:47:00 -0700 (PDT) Received: by 10.151.7.5 with HTTP; Thu, 22 May 2008 06:47:00 -0700 (PDT) Message-ID: Date: Thu, 22 May 2008 14:47:00 +0100 From: "James Strachan" To: camel-dev@activemq.apache.org Subject: Re: Camel and SCA In-Reply-To: <483528F9.2080308@skynet.be> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <17335281.post@talk.nabble.com> <48328C1C.8070309@gmail.com> <17398474.post@talk.nabble.com> <483528F9.2080308@skynet.be> X-Virus-Checked: Checked by ClamAV on apache.org Agreed - I guess someone could hack up a Tuscany plugin for Camel? 2008/5/22 Gert Vanthienen : > Vasil, > > > I'm not an SCA expert at all, but... > If you want to use Camel inside an SCA component, I think you should be able > to Tuscany's implementation.java or implementation.spring to do this. If > you hide the interaction with the other components behind a Java interface > as usual, it shouldn't matter if implementation is Camel or any other Java > code. You can choose to specify the Camel's routes in a java class or a > Spring configuration file and use that inside your SCA component. Camel > itself is just a JAR file you have to include in your (not sure about the > terminology either) SCA composite. It shouldn't be too hard to have > synchronous execution in Camel -- just avoid the typical asynchronous > concepts as seda: endpoints and you should be fine there. > > Suppose we would build a more specific implementation.camel for Apache > Camel, what additional features would you expect from that implementation? > > > Gert > > > > Vasil wrote: >> >> Hi Willem, >> >> I was thinking for using the route and pattern description power of Camel >> inside an SCA component for a more declarative description of integration >> scenario between services to which this component refers. I could have >> used >> BPEL or BPMN for example but this is rather complex and >> procedural-oriented, >> while I need mainly transformation capabilities with simple conditions >> (content-based router), split, agregate, filter, transform (XQuery for >> example), etc. in more data-oriented scenario. >> In this case the different connectivities (components) that Camel provides >> will not be needed as SCA cares for this and also anly synchronous working >> of the Camel engine will be used. >> >> Do you think this is feasible usage of Camel? >> >> Bye, Vasil >> >> >> willem.jiang wrote: >> >>> >>> Hi Vasil, >>> >>> AFAIK , we do not have any plan to integrate Camel with SCA. But you >>> could share you ideas with us in the mail list :) >>> >>> Willem >>> >>> Vasil wrote: >>> >>>> >>>> Hi, >>>> >>>> Is there any integration between Camel and SCA planned. If yes, can you >>>> share some more information. >>>> >>>> Bye, Vasil >>>> >>> >>> >> >> > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com