hi clay Privilege.JCR_ADD_CHILD_NODES indicates that you can create
child nodes (without explicitly specifying the primary or mixin types). if you wanted to use Node.addNode(String, String) you additionally have to grant Privilege.JCR_NODE_TYPE_MANAGEMENT. however, as far as other, non-protected properties are concerned that you want to add below your target node: as of Oak 1.0 (rewrite of the JCR repository) the Privilege.JCR_MODIFIY_PROPERTIES privileges has been adjusted to actually be an aggregation of _add_, _alter_ and _remove_ properties (thus reflecting the fact that some applications only want people to _add_ content but not provide them the ability to _modify_ it later on). those privileges are define in JCR but come with a 'rep' prefix. in the old jackrabbit 2.x this is not possible and Privilege.JCR_MODIFIY_PROPERTIES is not an aggregate privilege. hope that helps angela On 26/07/15 18:34, "Clay Ferguson" <[email protected]> wrote: >Fellow Jackrabbits, >I'm working on an "socia media" type application and trying to add a >feature that allows a user to share a node with another user, but the >person getting shared to should ONLY be able > to ADD child nodes, and not actually edit the node being shared. This >means I would like for Privilege.JCR_ADD_CHILD_NODES to actually do what >it's name implies. But it doesn't. It seems that in order to get >Privilege.JCR_ADD_CHILD_NODES to work, I *also* > have to include Privilege.JCR_WRITE which I specifically do NOT want. >Think of it like this: I have a blog node (for example), and I want >people to be able to make comments on my blog under it but not edit my >blog themselves. Am I doing something wrong? Should > this work? > > >The app is >meta64.com <http://meta64.com> if anybody cares. > > >β- β >Clay Fergu > >βsonβ > > > > >
