Dirk Verbeeck wrote:
> Indeed, you would expect that the status code from the lockMethod is kept.
> Maybe we can store the status, do setProperties and then set the status
> back ?
> Objections ?
Sounds reasonable.
> By the way, if you have testcases or even just examples please submit
> them. The slide community will be grateful and you will be sure this
> bug will be gone forever... If we don't forget to run the tests... ;-)
For example:
WebdavResource r = new WevdavResource("url to resource that exists");
r.deleteMethod(); // or any method that does setProperties after success
System.out.println("sc="+r.getStatusCode());
This results in sc=404 (although the DELETE method returns 200 OK, but the
PROPFIND generated from setProperties get a 404 Not found - as the resource
has been deleted).
For locking, LOCK/UNLOCK returns 200 OK/204 No Content, but the status is
207 Multistatus from the generated PROPFIND.