Hi Francesco, On Mon, Jan 28, 2019 at 5:36 PM Francesco Mari <[email protected]> wrote: > ...I would be more skeptical if I saw this code used in production overriding > or > enriching the behaviour of the API. Moreover, the JCR API encourages a very > fine-grained interaction with the underlying storage system and, because of > this reason, it's often on the critical path...
Fully agreed - for now our wrapper module is in the Sling Whiteboard, which clearly labels it as experimental. I have added a warning about that to the README at https://github.com/apache/sling-whiteboard/tree/master/jcr-wrappers - thanks for your comments! > ...- Use new and better abstractions to hide the JCR API.... I don't know if it's "better" but the Sling Resource Provider mechanism indeed allows one to plug various persistence mechanisms in a fairly simple way. But then of course it doesn't provide the same level of functionality than JCR, it's just focused on CRUD operations. -Bertrand
