jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger" <marcel.reuteg...@day.com>
Subject Re: "Unable to lock node. Node has pending changes: /counter"
Date Mon, 19 Jun 2006 14:56:31 GMT
On 6/19/06, Torgeir Veimo <torgeir@pobox.com> wrote:
> Would it be correct to call refresh(false) on the counter node in case
> of an exception? I only ever modify the value property when the node is
> created and in the generateNewResourceId() method.

yes, you should definitively handle that case. but after having a
second look at your code I realized that the counter node actually
doesn't get modified in the run method. It is only the property that
changes. So it seems there must be some code that modifies the counter
node outside of the Locked.run() method.

there are also some test cases that show how to use the utility:

Those test cases run fine on my checkout. and one of them
(LockTest.testSequence) does the same as your generateNewResourceId()
method, it increments a counter property.


View raw message