Return-Path: Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org Received: (qmail 40089 invoked from network); 6 Nov 2008 14:46:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Nov 2008 14:46:11 -0000 Received: (qmail 43248 invoked by uid 500); 6 Nov 2008 14:46:18 -0000 Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org Received: (qmail 43168 invoked by uid 500); 6 Nov 2008 14:46:17 -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 43142 invoked by uid 99); 6 Nov 2008 14:46:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Nov 2008 06:46:17 -0800 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 hzbarcea@gmail.com designates 74.125.92.145 as permitted sender) Received: from [74.125.92.145] (HELO qw-out-1920.google.com) (74.125.92.145) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Nov 2008 14:44:57 +0000 Received: by qw-out-1920.google.com with SMTP id 9so359194qwj.26 for ; Thu, 06 Nov 2008 06:45:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=mpu52WeCOVdw/99HRTIOD5BE7S4Anlgt5tMSRBOTbeU=; b=HVhSQ/KCBPTENWgfIaaHj4w4iu+EYjnxCfBu5iLHFYwOZw2aHEDmLZ1rzK9muDaOPs 65rsLBwWTSrh18geHztOqXnx8vAChQDDfFi8wpn2P5D1ceUWJ0GKc8LzpxUjeVHXn77L EdMNH19rKzf8H37ohqIfy3Qxz7TytmEiSerSw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=uA29wpDIe2NHTjQ4U05hUchxWADhsZ7oFG/7sQsjYNAhPO1lqJHPdW7fQJf2tdTyOp xSD57tXIynY/YtXMpm32sDbuEaCdVk+Mh+2yNoqZtwk08Ygz4pwWs2pQZ0elNqxe5/dX hyaPsKmQeuOJYReh8h+De99y93CKm7SGHJD2A= Received: by 10.214.25.15 with SMTP id 15mr2289852qay.119.1225982728730; Thu, 06 Nov 2008 06:45:28 -0800 (PST) Received: from ?10.40.68.51? (cpe-071-070-213-211.nc.res.rr.com [71.70.213.211]) by mx.google.com with ESMTPS id 6sm1608141ywp.3.2008.11.06.06.45.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 06 Nov 2008 06:45:28 -0800 (PST) Message-Id: From: Hadrian Zbarcea To: camel-dev@activemq.apache.org In-Reply-To: <4912EE68.9060501@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: [Discussion] - Camel 1.5.1 - What should we add and what not Date: Thu, 6 Nov 2008 09:45:25 -0500 References: <4C1FB9C00D24A140906239533638C4D205EC06A1@EXVS04.exserver.dk> <4912EE68.9060501@gmail.com> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org Yeah, that's not a problem. There's gonna be a big api change anyway. What I think is also important is fixing the dependencies (remove the =20= circular deps), this will allow us to move forward with a cleaner api. Hadrian On Nov 6, 2008, at 8:17 AM, Willem Jiang wrote: > It sounds good. > We'd better to be on the track of Camel 2.0 ASAP :) > > Willem > Claus Ibsen wrote: >> Hi >> >> Oh Willem wanted to do the verbs. Well he and Jonathan can get it =20 >> sorted. Willem could also continue doing his important work on =20 >> camel-cxf. >> >> Hadrian I doubt we have time to do anything for Camel 2.0.0 about =20 >> your great ideas of having the DSL auto generated. This is =20 >> something for the future such as Camel 3.0. 2.0 needs the API fixed =20= >> and improved performance without all the copying. And then better =20 >> camel-jbi integration as well. >> >> So I guess we should let Willem and Jonathan have green lights for =20= >> DSL renaming. >> >> >> >> Med venlig hilsen >> >> Claus Ibsen >> ...................................... >> Silverbullet >> Skovsg=E5rdsv=E6nget 21 >> 8362 H=F8rning >> Tlf. +45 2962 7576 >> Web: www.silverbullet.dk >> >> -----Original Message----- >> From: James Strachan [mailto:james.strachan@gmail.com] >> Sent: 6. november 2008 10:32 >> To: camel-dev@activemq.apache.org >> Subject: Re: [Discussion] - Camel 1.5.1 - What should we add and =20 >> what not >> >> Sounds good! >> >> >> 2008/11/6 Claus Ibsen : >>> Hi >>> >>> I propose a work plan such as: >>> >>> You and Hadrian should work on the remaining issues with =20 >>> refactoring the API to remove the generics and get it as correct. =20= >>> You are the best people for this work. Also very important that =20 >>> you guys look at the "remove unneeded copies of exchanges". >>> >>> Then Jonathan can work on the renaming of the DSL's. And he could =20= >>> also help removing the stuff that has been marked as @deprecated. =20= >>> He has already done some of this stuff before. And as a 2nd =20 >>> priority to find the gaps in the spring DSL vs. Java DSL. >>> >>> I would like to use this break to focus on the wiki documentation =20= >>> and my tutorial that I need to continue on part 5. >>> >>> >>> Med venlig hilsen >>> >>> Claus Ibsen >>> ...................................... >>> Silverbullet >>> Skovsg=E5rdsv=E6nget 21 >>> 8362 H=F8rning >>> Tlf. +45 2962 7576 >>> Web: www.silverbullet.dk >>> >>> -----Original Message----- >>> From: James Strachan [mailto:james.strachan@gmail.com] >>> Sent: 6. november 2008 10:20 >>> To: camel-dev@activemq.apache.org >>> Subject: Re: [Discussion] - Camel 1.5.1 - What should we add and =20 >>> what not >>> >>> 2008/11/6 Claus Ibsen : >>>> Hi >>>> >>>> Yeah could be a good idea to let 2.0.0 solely be focused on =20 >>>> changing the API. >>>> - generics >>>> - verbs for DSL >>>> - remove @deprecated stuff >>>> >>>> And then we can be back on track with hammering 200+ issues every =20= >>>> 3rd month. >>> Yeah! I kinda think we should focus almost exclusively on the stuff >>> that might result in API changes ASAP. e.g. how fast can we get =20 >>> Camel >>> when its being used as a JMS <-> JMS router or a JBI <-> JBI router. >>> >>> >>> -- >>> James >>> ------- >>> http://macstrac.blogspot.com/ >>> >>> Open Source Integration >>> http://fusesource.com/ >>> >> >> >> >