I've tracked this down to the code that processes lockdiscovery properties returned in the propfind. There is a call to DOMUtils.getTextValue() in LockDiscoveryProperty.java and this call is returning NULL instead of the CDATA that was returned by the server in the D:owner element. Its because the code is checking whether the element is a text node and only returning the value if it is. Since the D:owner contains CDATA its not matching and returning a NULL result instead.
If anyone has already fixed this then let me know otherwise I'm going to see whether changing getTextValue() to look for CDATA nodes as well will fix it. Warwick -----Original Message----- From: Warwick Burrows [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 10:30 AM To: 'Slide User Group ([EMAIL PROTECTED])' Subject: lock owners not returned with lock properties in 2.1b1?? Hi, It seems that lock owners are not returned from the server with the other lock information any more. I've seen this from the CLI and from within my own application. I noticed it when the application that I had working with 2.1M1 stopped working with 2.1B1. When I lock a resource with an owner using "-o<name>" the command succeeds and a locktoken comes back. But when I run "locks" on the object the owner name is empty. Has anyone else seen this problem or can suggest why this is happening? I'm running with security checking disabled but I don't see why that would affect locking which is enabled. Thanks, Warwick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
