Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of david.nuescheler@gmail.com
 designates 72.14.204.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=b1iV32PeEcdfnlaO4KGX47yJ4n2huMQwNstERn3DasXh3DTk5hBY2EYDdS/eDL9zdP/jqmVa9tJ4n0X/+OBp+mDdv+O6jdm5cMWcs8WEtY95KI79Sqw452n1+SicFVYfzQwxNu+4oBCrO6FyvrSm7XIyp6S6g08fx41KLMYVj64=
Message-ID: <eb7e2190510130340g27b9ac3by70de75e01ab3d8b0@mail.gmail.com>
Date: Thu, 13 Oct 2005 12:40:06 +0200
From: David Nuescheler <david.nuescheler@gmail.com>
Reply-To: david.nuescheler@day.com
To: jackrabbit-dev@incubator.apache.org
Subject: Re: Confused about checking permissions
In-Reply-To: <8fa1023f0510130330q540b3f73x1347a615b71a1506@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8fa1023f0510130322t7b8d71d4uc94566a5189d0d4e@mail.gmail.com>
	 <90a8d1c00510130328u305aaae9hf2efa81c17d88fe4@mail.gmail.com>
	 <8fa1023f0510130330q540b3f73x1347a615b71a1506@mail.gmail.com>

> Yes, but AccessManager is jackrabbit-dependent, no? i.e. is not part of t=
he
> spec.
yes, that's true.

the only part of access control that made it into jsr-170 or (jcr v1.0) is
the introspection of the permissions. not the management of permissions.

this is in-line with the exclusion of all the management interfaces
(nodetypes, workspaces, ...) from v1.0 of jcr.

see jsr-283 (v2.0 of jcr) for further development on that, but for now you =
will
have to resort to proprietary mechanisms of the repository.
however, the access control "management" portion normally does not make
for a lot of source code in most applications that i am familiar with,...

in addition to that a number of repository implementation are based
on jackrabbit and therefore expose the same or similar interfaces
as jackrabbit, so using the jackrabbit interfaces may be a good choice in
the first place.

regards,
david