Sorry...here it is (early morning here) [1]. Unfortunately, it doesn't
say much more than my first post ;-)
[1] http://markmail.org/message/bea62gkwcknkw3hp
Vidar Ramdal wrote:
On Fri, Mar 6, 2009 at 3:44 PM, Rory Douglas <[email protected]> wrote:
Prior to Jackrabbit 1.5, I did similar work for an ACL-based AccessManager
(see [1]). The difference was I hacked the server bundle to export the
desired classes & created an AccessManagerFacade that would load up
implementations from bundles.
You can look at o.a.s.jcr.jackrabbit.server.security.LoginModulePlugin and
o.a.s.jcr.jackrabbit.server.impl.security.PluggableDefaultLoginModule for
another approach that doesn't require exporting core Jackrabbit classes, but
does require providing delegate classes for any core API you want to expose
outside the jackrabbit-server bundle.
Interesting, thanks!
So, maybe the best approach would be a PluggableAccessManager. What do
you guys think?
I could have a shot at implementing it, if you think it's a good idea.
BTW, I think you forgot the link [1] - I'd really like to see it :)
--
Rory Douglas | Senior Principal Consultant
Fax: +1-201-604-6428 | Mobile: +1-917-498-5344
Oracle North America Consulting
ORACLE United States | | San Diego, CA
"Please consider your environmental responsibility before printing this
e-mail"
