Angela Schreiber wrote:
Marcel Reutegger wrote:
Carsten Ziegeler wrote:
Now, this may be a dumb question, but why this move?
that was probably by mistake.
i don't think so. and it was made on intention.
Ok, let me explain my use case: the Node.lock() method does not
guarantee that I get the lock; it does not wait if there is already
a lock on the node (or a child node).
So, if I need a lock on a node, I've usually to do exactly what
the Locked class does - waiting until I'm able to get hold of the lock.
I think this code is pretty useful for application code.
But perhaps this is something which should be added to the spec as well
for JSR 283? Something like a Node.waitForLock() (or whatever method
name is best)?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
