jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@adobe.com>
Subject Upgrade to Oak and Mandatory CommitHooks
Date Thu, 10 Apr 2014 06:55:41 GMT
Hi Jukka

We had an issue during upgrade testing from jackrabbit to oak that seemed
to be 
caused by a missing commit hook (PermissionHook) as the access control
was present after the upgrade but the entries in the permission store were
missing altogether.

When thinking about it I realised that this problem may also be present for
all other commit hooks that are present and mandatory for a JCR repository
on oak: all those defined by the various security related parts (e.g
VersionablePathHook, JcrAllCommitHook) as well as the version editor and
so forth.

If my analysis for the issue described above was right and you are about to
fix it, I would be very glad if you could verify that all the required
commit hooks are in place. IMHO it would also make sense to have all the
enabled in order to detect possible inconsistencies early during the
instead of having weird repository behaviour later on which are hard to

Kind regards

View raw message