On Fri, Aug 21, 2009 at 8:55 AM, Gamba<[email protected]> wrote: > > Ok, that's correct. But the behaviour is the same as before, when I login > with a new session: > > ... > > // only with this snippet unlocking is performed > //nodeToLock.unlock(); > sessionLocal.logout(); > sessionLocal = null; > > // After logout, we have to create a new session to check the locking. > // Does only make sense in multiple transactions? > sessionLocal = repository.login (new SimpleCredentials("..", > "..".toCharArray()), "default"); > > // Get node to update ... > Node rootNode2 = sessionLocal.getRootNode(); > Node nodeFree = rootNode2.getNode("HMG"); > > assertFalse("Node is still logged, after session-logout", > nodeFree.isLocked()); > sessionLocal.logout(); > > => Exception: Node (nodeFree) is still locked. I expected that the lock > would be released > after session-logout because the sessionScoped-Param is ste to true.
Looks like a bug, maybe only in the RMI client, as the jcr tests cover that: [1] (testLogout()). Do you use the latest version of Jackrabbit (1.6.x)? Could you test it without RMI and/or file a JIRA bug? Thanks! [1] http://svn.apache.org/viewvc/jackrabbit/branches/1.6/jackrabbit-jcr-tests/src/main/java/org/apache/jackrabbit/test/api/lock/LockTest.java?revision=801262 Regards, Alex -- Alexander Klimetschek [email protected]
