You are viewing a plain text version of this content. The canonical link for it is here.

Posted to slide-dev@jakarta.apache.org by Robert Owen <eu...@sas.com> on 2001/10/11 13:39:42 UTC

Empty supportedlock or lockdiscovery causes parsing problems

An empty supportedlock element returned from a PROPFIND (<a:supportedlock/>
as in IIS for example) causes a NullPointerException at line 176
(getPropertyAsString) of SupportedLockProperty in the webdav client, as the
locks value returned is null and there is no guard against this.

An empty lockdiscovery element returned from a PROPFIND (<D:lockdiscovery/>
as in Apache for example) causes a NullPointerException at line 236
(getPropertyAsString) of LockDiscoveryProperty in the webdav client, as the
locks value returned is null and there is no guard against this.

Re: Empty supportedlock or lockdiscovery causes parsing problems

Posted by Dirk Verbeeck <di...@pandora.be>.

Robert Owen wrote:
> 
> An empty supportedlock element returned from a PROPFIND (<a:supportedlock/>
> as in IIS for example) causes a NullPointerException at line 176
> (getPropertyAsString) of SupportedLockProperty in the webdav client, as the
> locks value returned is null and there is no guard against this.
> 
> An empty lockdiscovery element returned from a PROPFIND (<D:lockdiscovery/>
> as in Apache for example) causes a NullPointerException at line 236
> (getPropertyAsString) of LockDiscoveryProperty in the webdav client, as the
> locks value returned is null and there is no guard against this.

Thanks for the report!
It is logged as bug 4131 and is already fixed ;-)

Can you verify if this fix solves you problems.


Dirk