On 2012-01-10 11:34, David Buchmann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1hi, while implementing locking for the phpcr implementation jackalope that talks with the jackrabbit davex backend, we tried to understand locking in jackrabbit. but the following code does what we would expect: Session s = repo.login(sc,workspace); Node t = s.getRootNode().addNode("test", "nt:unstructured"); t.addMixin("mix:lockable"); s.save(); LockManager m = s.getWorkspace().getLockManager(); Lock l = m.lock(t.getPath(), false, true, 1, "me");
1 second sounds short :-)
System.out.println(l.getSecondsRemaining()); it prints 2147483 is this feature not implemented in davex? it seems to me that the server is neither respecting the timeout of 1 second, nor that this should be session scoped. it just makes a lock that stays until i restart jackrabbit. is there a jira issue to track that? i searched for lock and timeout but did not find anything related to davex. ...
I wouldn't be surprised if there a bugs left in this area. If it's possible, it would be great to see an HTTP trace to see what's going on on the wire.
Best regards, Julian
