Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 72622 invoked from network); 14 Jul 2009 09:15:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jul 2009 09:15:20 -0000 Received: (qmail 89509 invoked by uid 500); 14 Jul 2009 09:15:30 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 89486 invoked by uid 500); 14 Jul 2009 09:15:30 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 89476 invoked by uid 99); 14 Jul 2009 09:15:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 09:15:30 +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 claus.ibsen@gmail.com designates 209.85.220.208 as permitted sender) Received: from [209.85.220.208] (HELO mail-fx0-f208.google.com) (209.85.220.208) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 09:15:21 +0000 Received: by fxm4 with SMTP id 4so2404503fxm.20 for ; Tue, 14 Jul 2009 02:15:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=9GWWWWgnB+xCaCooH/OI6gP7bSiaMGv3A0W0G48dHS0=; b=C3McEz/HSuxLmvpZJhux3nUEQ9DOMjhA3hzZuYkXo+FsRBpKOYv49gga/T3lSbPwYx mLLxIiKAggfmmrSQM/YYif+xyX/IUNE4BPjVeCxNDHHpv5QXbXsiGzo1UwuqcwXGYAzY zqurcwoBMHTmb70UD0UWajxpn+4CsdKVty+2A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=vEnhoPZGVy/suq7c4VvCzM2034RhxajuW8UlTTKrxFY7QJIBPLItwo5vpHpEdUzi3D VQ70mwSOH52WoUGDsjJ1MEiqrhOegb3YRdnpDJ4qzIIkufw8AAE//KXJg+CTOOZFTNTI oI4fZnf3FtFWzIUpjAkmMibQgF4aMMcXwheKc= MIME-Version: 1.0 Received: by 10.223.125.144 with SMTP id y16mr2624330far.93.1247562901145; Tue, 14 Jul 2009 02:15:01 -0700 (PDT) In-Reply-To: References: <5380c69c0907120223i33d3b687l3df885c96cba5aab@mail.gmail.com> <5380c69c0907130920t1c243aafwd3ce59ba844c570d@mail.gmail.com> <5380c69c0907131051i1ed6d881qf410ad5bf0727f16@mail.gmail.com> <5380c69c0907140149o24726f88l5e8c8afc5b44dcef@mail.gmail.com> From: Claus Ibsen Date: Tue, 14 Jul 2009 11:14:41 +0200 Message-ID: <5380c69c0907140214s22a94636m45836b95297344f@mail.gmail.com> Subject: Re: [DISCUSS] Semantics of IN and OUT (was: Faults and Exceptions in Camel) To: dev@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > Yeah. > > BTW we could leave getIn() and getOut() & try implement the > ImmutableWrapper and CopyOnWriteFacade for In/Out respectively and try > them out inside the current API - before we go ahead with any kind of > renaming of getIn() and getOut(). > > Maybe we could even keep getIn() / getOut() around for 2.0 (and zap in > 2.1) and leave deprecated and make them just delegate to the new > method names (say getInputMessage() and getMessage()). The deprecated > message could then describe how folks typically should switch > getIn()/getOut() to using getMessage() unless they really really want > the immutable input message getInputMessage(). > Brilliant idea and a good migration path as well. And it wont delay Camel 2.0 as much as a full blown migration would have done.