Hi, On Wed, Sep 12, 2012 at 10:37 AM, Thomas Mueller <[email protected]> wrote: > Yes, that would work as well. I have added that to OAK-300. The > disadvantage is that it's a new API (not part of the JCR specification). > The two options I proposed don't require a new API.
There's no need for the Oak API to reflect JCR in all its details. If there's a better way to design something, we should do so as long as it's still possible for oak-jcr to implement the relevant parts of JCR based on the underlying Oak API. BR, Jukka Zitting
