On Dec 16, 2010, at 4:50 AM, Alessandro Novarini <[email protected]> wrote:
> Yes, I agree with you, but I don't think that would be enough because if you > search the work 'jackrabbit' in the Sling sources, you'll find several > projects with references to jackrabbit specific classes. > I guess those classes need to be adjusted to be unawared of the JCR specific > implementation underneath. I don't think that's possible. In general, Sling only depends upon Jackrabbit when there isn't a JCR API we can use. For example, user management. So, yes, a full Sling-on-Modeshape implantation would really need new user and access management bundles (or maybe an SPI interface). But I don't think these are critical. That said, if you or anyone else has ideas for additional decoupling of Sling from Jackrabbit, please submit patches. Also, if multiple people are going to work on Sling-on-Modeshape, perhaps that'd be a good project for apache-extras.org. WDYT? Justin > > Thanks > Ale > > On Dec 15, 2010, at 7:03 PM, Justin Edelson wrote: > >> It would probably be better to use the >> org.apache.sling.jcr.jackrabbit.server bundle. That's likely the one a >> ModeShape would need to replace. > > >
