atom feed7 messages in org.apache.jackrabbit.devRe: Content explorer (Re: Jackrabbit ...
FromSent OnAttachments
Greg KlebusApr 20, 2008 3:21 pm 
Paco AvilaApr 21, 2008 4:22 am 
Jukka ZittingApr 21, 2008 9:05 am 
Angela SchreiberApr 22, 2008 12:10 am 
Greg KlebusApr 22, 2008 1:40 am 
Tobias BocanegraApr 22, 2008 8:15 am 
Jukka ZittingApr 22, 2008 8:21 am 
Subject:Re: Content explorer (Re: Jackrabbit 1.5 release plan)
From:Jukka Zitting (jukk@gmail.com)
Date:Apr 22, 2008 8:21:41 am
List:org.apache.jackrabbit.dev

Hi,

On Tue, Apr 22, 2008 at 10:11 AM, Angela Schreiber <anch@day.com> wrote:

Jukka Zitting wrote:

I guess we'd disable the ACL editor in Jackrabbit 1.5, and bring it back in Jackrabbit 2.0 when Angela's work for JSR 283 access control is finished.

it's already committed to jackrabbit trunk. i just didn't change the default configuration yet to the in-spe default implementation, since there are still known issues and since i didn't take a closer look a performance optimization yet.

Cool! Then I think we can keep the ACL editor, as long as someone adapts the implementation to the JSR 283 access control API (or a Jackrabbit-specific lookalike).

BR,

Jukka Zitting