From users-return-13605-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Fri Dec 04 14:21:37 2009 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 90363 invoked from network); 4 Dec 2009 14:21:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Dec 2009 14:21:36 -0000 Received: (qmail 85174 invoked by uid 500); 4 Dec 2009 14:21:36 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 85128 invoked by uid 500); 4 Dec 2009 14:21:35 -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 85117 invoked by uid 99); 4 Dec 2009 14:21:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2009 14:21:35 +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 fmeschbe@gmail.com designates 209.85.218.214 as permitted sender) Received: from [209.85.218.214] (HELO mail-bw0-f214.google.com) (209.85.218.214) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2009 14:21:25 +0000 Received: by bwz6 with SMTP id 6so2024222bwz.11 for ; Fri, 04 Dec 2009 06:21:05 -0800 (PST) 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:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=/ZqD7BrsCI1jUIv2SzWdX1W7h5b8W/gdEzlxyS1ahV4=; b=ZJ/8JTgXLzIsicDYrF/9z7WGP0H/QzRqe1i0ucqUnPufXQt9soDP7OWM9PQIpaddLI 5Z33JpaAK9QXWcUeDh/gYXtzwudh3gxeSyNQuxhPxhcYFbqwH/nTdA4Bg2ORrYPHWN6k KYXTsDzFnWgIj+cSnFccP4gaK7QC+erIh9G1I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=UiaP3+bTwWGmdLjDyJQ9oWHD9Z7D8QvlG9hm9z6qQzpvKHYwsRtT4KW4f0ys5oYjiH 62lMDJ2HmVb1VKaH7KAr4UfrQ1sri1O8qPM0kxSb0trjEVttHB690lPl1kN4iGpGl10C iUzh1TOyfZSgsm7YoLx4w4NRMHPdar4emcctA= Received: by 10.204.151.194 with SMTP id d2mr89738bkw.85.1259936464030; Fri, 04 Dec 2009 06:21:04 -0800 (PST) Received: from ?192.168.1.20? (cable-static-138-82.eblcom.ch [87.102.138.82]) by mx.google.com with ESMTPS id 14sm1107210fxm.15.2009.12.04.06.21.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 04 Dec 2009 06:21:03 -0800 (PST) Message-ID: <4B191ACE.2000103@gmail.com> Date: Fri, 04 Dec 2009 15:21:02 +0100 From: Felix Meschberger User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: users@jackrabbit.apache.org CC: Sling Developers Subject: Re: Recommended way to take deal with JCR-1984 References: <1BD29549-07A4-4B17-B63B-FAC6B597EEAB@tfd.co.uk> <4B17F912.809@day.com> <7F8FD9A8-F095-4565-885E-8DC66D758CD3@tfd.co.uk> <4B1823AC.8030405@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Ian Boston schrieb: > Felix, > yes thank you, > got the update through which did as you say fix about 4 of the tests in > Sling (and found the sling jira now). > BTW I think the other problems I am having with {internal}privileges not > being defined are of my own making, ok. > although I did notice the launch-pad > tests are using 2.0.4-incubator of JCR Base rather than 2.0.5-SNAPSHOT > which is in the code base so upgrading the JR API to 1.6 in the current > trunk wont flow through. (not that it fixes any of the remaining tests) Yes, but this doesn't matter because the jcr/base module just provides AccessControlUtil class, which is pure API calling. This doesn't matter whether it is 1.5 or 1.6. In fact updating the access manager dependency to the SNAPSHOT fixed the tests (after fixing the access manager bundle). Regards Felix ... end of crossposting ;-) > Ian > > (ccd dev@sling) > > On 3 Dec 2009, at 20:46, Felix Meschberger wrote: > >> Hi Ian >> >> In fact I rewrote a Sling integration test just this morning exactly >> doing such property setting for verification purposes (the test used to >> check the rep:principalName property which is not available as such any >> longer). >> >> Regards >> Felix >> >> Ian Boston schrieb: >>> Angela, >>> Fantastic, >>> I misread the patch forgetting that * might be allowed. >>> Thank you. >>> Ian >>> >>> On 3 Dec 2009, at 17:44, Angela Schreiber wrote: >>> >>>> hi ian >>>> >>>> JCR-1984 addressed a problem that protected properties defined >>>> by the user/group node types were exposed by the #getPropertyNames >>>> and #getProperty methods, although they could not be modified >>>> by the corresponding set/remove methods. >>>> >>>> this issue should not affect additional, application specific >>>> properties that were or will be stored with a user/group. >>>> the nodetype still allows for >>>> >>>> - * (UNDEFINED) >>>> - * (UNDEFINED) multiple >>>> >>>> and those props should be exposed by the mentioned methods. >>>> i'm not aware of any change that would have broken this. >>>> >>>> angela >>>> >>>> >>>> >>>> Ian Boston wrote: >>>>> Hi, >>>>> IIUC [1], post 1.6 blocks an authorizable node from holding any >>>>> properties, other than those listed in the schema. >>>>> How do I add and retrieve a well defined set of properties for the >>>>> node as was possible in JR15 ? >>>>> We have an application that stores extra group and user metadata on >>>>> the authorizable node and I really don't want to have to rewrite it. >>>>> Thanks >>>>> Ian >>>>> 1 https://issues.apache.org/jira/browse/JCR-1984 >>>> >>> >>> > >