jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mat Lowery <mlow...@pentaho.com>
Subject setPolicy requires checkout?
Date Wed, 21 Mar 2012 17:06:43 GMT
According to the JCR 2.0 API documentation of 
AccessControlManager#setPolicy(String, AccessControlPolicy):

"A VersionException will be thrown either immediately, on dispatch or on 
persists, if the node at absPath is read-only due to a checked-in node. 
Implementations may differ on when this validation is performed."

Doesn't this assume too much about the implementation?  Using Jackrabbit 
2.0.4 defaults, rep:policy's onParentVersion is IGNORE so it technically 
doesn't require a checkout but the implementation actually does make 
sure it is checked out in ProtectedItemModifier.

I'd like to make an ACL modification without creating a new version.  
Any ideas?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message