Tommaso Teofili created JCRVLT-128:

             Summary: System maintained cache nodes should be ignored
                 Key: JCRVLT-128
             Project: Jackrabbit FileVault
          Issue Type: Bug
    Affects Versions: 3.1.28
            Reporter: Tommaso Teofili

In OAK-3003 a persisted [principal 
cache|] was 
introduced that creates _rep:cache_ nodes under authorizables.
Creating a package for such authorizables will result in including the cache 
node in there, which sounds wrong as that node is an implementation detail 
which doesn't make sense to install anywhere; however that can be avoided by 
proper filters.
What is problematic is the installation phase, if an authorizable gets packaged 
with FileVault (no rep:cache in the package) and the target user/group has a 
rep:cache node itself the importer will try (and fail as it's protected) to 
delete the persisted cache node unless the ImportMode is set to MERGE.
In my opinion this is wrong, it should be possible to not touch such nodes on 
package installation, regardless of the chosen ImportMode.

This message was sent by Atlassian JIRA

Reply via email to