Am 21.04.2021 um 10:18 schrieb Konrad Windszus:
Thanks, that makes it even more blurry for me what is supposed to be exposed by Jackrabbit API vs by Oak API if Oak is now the only implementation of more recent Jackrabbit API versions... ...
AFAIU: - Jackrabbit API *extends* the JCR API; so it is for situations where you access the repo using the JCR API, but need a few extensions - Oak API should only be used if you're ok to depend on Oak as JCR implementation. Not sure about what stability guarantees there are - Jackrabbit API is implemented by both classic Jackrabbit and Oak (it's just that some features might not be available when using classic Jackrabbit). Best regards, Julian
