[
https://issues.apache.org/jira/browse/JCR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-792.
-----------------------------------
Resolution: Invalid
i ran your test code (against svn trunk). here's the console output:
freshDB true
checking permission on /
checking permission on /
checking permission on /newNode/jcr:primaryType
checking permission on /newNode/ext:name
checking permission on /newNode/jcr:uuid
so everything seems to be working as expected....
please note that the access manager will be invoked
*before* the changes are actually committed,
i.e. new nodes and properties are not yet visible
to other sessions.
> after enabling access manager, I can't createNode and setProperty without a
> node.save in the middle
> ---------------------------------------------------------------------------------------------------
>
> Key: JCR-792
> URL: https://issues.apache.org/jira/browse/JCR-792
> Project: Jackrabbit
> Issue Type: Bug
> Components: security
> Affects Versions: 1.2.3
> Reporter: Xiaohua Lu
> Attachments: jaas.config, JackrabbitTest.java, ntExts.txt,
> TestAccessManager.java, TestLoginManager.java
>
>
> I added my own access manager. after that I can't get the following code
> working
> Node n = createNewNode(parentNode);
> n.setProperty();
> parentNode.save();
> It seems that setProperty will invoke access control check, but since the new
> node is not in the repository yet, my access manager implementation won't be
> able to grant permission. I also tried to use hierachyManager to get the path
> of the new node, it also returned null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
