jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@adobe.com>
Subject Re: Time for jackrabbit-jcr-auth?
Date Tue, 19 Feb 2013 10:02:59 GMT

Can you separate API from implementation in the same step ?

Currently API and implementation is "nicely" mixed, which makes it close to impossible to
properly use in an OSGi context.


Am 19.02.2013 um 10:52 schrieb Jukka Zitting:

> Hi,
> When looking at the login() code for OAK-634 I realized that there's a
> a lot of duplication between jackrabbit-core and oak-core in this
> area.
> Would it make sense to split out the authentication code to something
> like jackrabbit-jcr-auth that could be used by both jackrabbit-core
> and oak-core.
> AFAICT there aren't too many places in the authentication code that
> require deep integration with the repository internals (unlike in
> authorization), so it should be possible to extract the relevant code
> to a separate component. Or am I mistaken?
> BR,
> Jukka Zitting

Felix Meschberger | Principal Scientist | Adobe

View raw message