On 25.06.2014, at 15:35, Dominik Süß <[email protected]> wrote:
> this isn't true anymore, the session.save() in the POST Servlet is > triggered through the resourceResolver.commit() [0] - and direct > session.save() should not be performed anymore Ok, I see, didn't know. > The mechanism I propose is bound to resourceResolver but does not prevent > JCR API access beside the fact that session.save() would not be a complete > resourceresolver.commit (which would still have pending changes aka the > events). If you ask me, this is still an abstraction leak and probably very confusing to someone new. Cheers, Alex
