jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niu, Xuetao" <Xuetao....@fiserv.com>
Subject RE: "Bad Request" exception using DavEx
Date Thu, 18 Mar 2010 15:32:42 GMT
I tried LockManager.unlock("/") right before the session.save(), but it
throws an LockException telling "No lock present on Node with id /". 

Very strange... Does it mean it hasn't been locked at all?

> if you lost the token it is written somewhere on the
> filesystem (i don't recall the location by heart).

- I believe it is the .lock file that I explicitly deleted.

Xuetao

-----Original Message-----
From: Angela Schreiber [mailto:anchela@day.com] 
Sent: Thursday, March 18, 2010 4:21 PM
To: users@jackrabbit.apache.org
Subject: Re: "Bad Request" exception using DavEx

Niu, Xuetao wrote:
> Hi Angela,
> 
> Could you try this? Remove an existing node, save session, and add
that
> node again:

in the trunk it works for me. and i'm not aware of a recent
fix that would have changed that (see JIRA for the list of
recently fixed bugs [1] and [2] for the list of known issues).

if the error you see in the log is in relation to your
problem then it's for sure a lock on the root that prevents
you from updating the node.

use LockManager#unlock or Node#unlock to get rid of the
lock... if you lost the token it is written somewhere on the
filesystem (i don't recall the location by heart).

and no: adding the mixin doesn't automatically lock the
node.
and no: the root isn't locked by default.

a lock is only created if you explicitly ask for it.
have a look at JSR 170 or 283 for the details.

angela

[1] query for
     components: jcr2spi, spi2dav and jcr-server,
     fixversion: 2.1
[2] 
http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-spi2dav/pom.
xml


Mime
View raw message