On Tue, Nov 16, 2010 at 4:54 AM, Felix Meschberger <[email protected]> wrote: > One thing that may break is the node type loading functionality of the > jcr/base bundle. This uses Jackrabbit API which is not standardized > (There is in fact an old issue to replace this implementation with an > implementation leveraging the official JCR node type management API).
This is no longer true. Node Type loading now uses classes from jackrabbit-jcr-commons which should work against any JCR 2 implementation. The bits in jcr.base which *are* dependent upon Jackrabbit are in AccessControlUtil (actually, there's one more reference in AbstractSlingRepository, but that doesn't need to be there and I'll commit a fix soonish). We could probably make the import of o.a.jackrabbit.* optional for jcr.base. In general, this is probably true across the board - anything related to access control (i.e. ACL loading in content loader) is dependent upon Jackrabbit. Everything else *should* be JCR only. Of course, it'd be great to have someone actually test this out with ModeShape or another non-Jackrabbit (or CRX) implementation. Justin
