jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Müller <thomas.muel...@day.com>
Subject Re: Sling's use of Jackrabbit
Date Mon, 30 Nov 2009 13:23:38 GMT

>> I would not move the API to the Jackrabbit API. Just moving the
>> interfaces into sepatate packages, eg. below o.a.j.core.api would
>> suffice it to export this space and leave the implementation private.
> +1
> Moving the persistence manager interface and co (basically everything
> that can be swapped by custom implementations in the repository.xml)
> into a separate API package is a good idea. But it makes sense to
> separate this from the client-side API in jackabbit-api and only have
> this as an exported package in jackrabbit-core.


As I already wrote, it doesn't make sense to do that now. We can still
do that later on, when there is actually somebody that needs it.


View raw message