jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaohua Lu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-792) after enabling access manager, I can't createNode and setProperty without a node.save in the middle
Date Fri, 16 Mar 2007 16:24:09 GMT

     [ https://issues.apache.org/jira/browse/JCR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xiaohua Lu updated JCR-792:
---------------------------

    Attachment: jaas.config
                ntExts.txt
                JackrabbitTest.java
                TestAccessManager.java
                TestLoginManager.java

Hi Stefan, 

I have composed a test case and hopefully it will be helpful. But conceptually, if one session
has node and property set, before commit, the other session should not see it, or am I wrong?
(my implemenation of access manager is using another session compared to the test code)

step to reproduce :
1. copy the file to a directory 
2. copy required jar files to lib directory 
3. compile the code and run  JackrabbitTest 

Let me know how it goes.

Thanks.

Xiaohua 










> 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.


Mime
View raw message