> > Pros: > > > > - to work with the underlying repository, we can use JCR API directly > > (can we?) > > If you want to access the JCR API directly from the non-Sling part, you > will be able to do so if the non-Sling part is part of the same OSGi > runtime. >
It's been a while but I've used remote access to the JCR before. https://wiki.apache.org/jackrabbit/RemoteAccess On a personal note, I would avoid JCR level manipulations and if possible stick to the Sling API. You'll discover that that you'll be writing a lot of boiler plate only to find that the Sling has come up with a graceful way of handling it already. -- Jason
