From users-return-4162-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Fri Jul 20 17:37:54 2007 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 59611 invoked from network); 20 Jul 2007 17:37:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jul 2007 17:37:53 -0000 Received: (qmail 44647 invoked by uid 500); 20 Jul 2007 17:37:54 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 44626 invoked by uid 500); 20 Jul 2007 17:37:54 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 44617 invoked by uid 99); 20 Jul 2007 17:37:54 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 10:37:54 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of the.mindstorm.mailinglist@gmail.com designates 209.85.146.180 as permitted sender) Received: from [209.85.146.180] (HELO wa-out-1112.google.com) (209.85.146.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 10:37:50 -0700 Received: by wa-out-1112.google.com with SMTP id m34so1361902wag for ; Fri, 20 Jul 2007 10:37:30 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=phpBNdXOn05VMroCtvY5OQ3U+v6alg0yM6KPR2AuU6uAjR7z/63ZT+x+fXGCxm4n19Zl1PQyj/bucSbSylr2RtzKMP33mF0p/oJi9eRLcxi16/MFD1kV6xyWAYLz0PSaWbBxfcHBTk8SOS/MwhyJG+N4tvxozbrhRFYOPCyhL94= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TaNhxle349xbRuElPB9ZkPb9DAsPI1w2oyCeoBjD2h2MjwUhyVVPo65NvqlPaRHF69p/RNoBuUDIX8rxXdyVQ7WHo74YvZK5DMawD/PBSWzraN7dhgMPKYFgbPYYA73eW9KHGyvimfXvbUZv7GJUt6fXAXGDgxSuyc1h99PwPNg= Received: by 10.114.76.1 with SMTP id y1mr659164waa.1184953050173; Fri, 20 Jul 2007 10:37:30 -0700 (PDT) Received: by 10.114.150.12 with HTTP; Fri, 20 Jul 2007 10:37:30 -0700 (PDT) Message-ID: Date: Fri, 20 Jul 2007 20:37:30 +0300 From: "=?UTF-8?Q?Alexandru_Popescu_=E2=98=80?=" To: users@jackrabbit.apache.org Subject: Re: 3.1.3.1 Removing Items In-Reply-To: <510143ac0707201018p53ca033eia60c7e402d5cc429@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <469F7E7C.4090906@yourmail.com> <46A06905.5070008@gmx.de> <8641fd7c0707200149k6d7115bau555dc568801fee28@mail.gmail.com> <8641fd7c0707200355i605e8f96x7251863e2f5f51c4@mail.gmail.com> <46A0E990.1000204@yourmail.com> <510143ac0707201018p53ca033eia60c7e402d5cc429@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 7/20/07, Jukka Zitting wrote: > Hi, > > Everyone, I don't think this thread is getting us anywhere at the moment. > > There are many cases (like setProperty(null)) where the JCR 1.0 API > could have been designed otherwise, but complaining about it doesn't > really help anyone if you don't have an idea of how to fix that. > > Note also that for an idea to have a reasonable chance of being > accepted in JCR 2.0, it *needs* to be backwards compatible. So for > example we can't just declare that setProperty(null) will start > throwing NullPointerExceptions, as that's bound to break a whole lot > of existing clients. > > Of course I'm all ears (and I believe the whole JSR 283 expert group > at jsr-283-comments@jcp.org is) for good suggestions where things > could be improved, but just complaining that a feature doesn't work > like you want or suggesting obviously incompatible changes doesn't > really get us anywhere. > Sorry Jukka, but I don't really feel we were complaining here, but rather describing the problem so that everybody has chance to see our reasoning. And the initial post started with the proposal. Now about the compatibility issue: considering that 2.0 is suggesting the removal of XPath we cannot talk about backward compatibility anymore. One more change at the API level and one that will make things clearer is the smart decission (remember we are not talking about a 1.1 spec, but about 2.0 which is already suggesting non-backward compatible changes). bests, ./alex -- .w( the_mindstorm )p. > BR, > > Jukka Zitting >