(a) Vista does locking even if the resource says it does not support LOCK.
A proposed solution is found in attachment "issue-2-proposed-vista-fake.patch":
When the MiniRedir tries to do a LOCK, but the original resource returned "405"
(NOT ALLOWED), which means that either the method is not implemented by the
resource or the user has no right to obtain a lock, the Interop Filter jumps in
and instead sends a slightly different "interpretation" of the response to the
client, while not really sending a lie: The answer sent back is that the LOCK
method was accepted (which is true, since the Interop Filter processed it), but
the current lock is a shared one for any user and it has a timeout of zero
seconds. That means, the semantics of the results are unchanged, but just the
technical way to tell it to the client is changed. This is a very smart
solution, and it is working on Vista Business.
(b) Locking support has some bugs in both, webdav-jaxrs and webdav-addressbook.
Just posted a question to the Jersey Mailing list, hoping to get some help. As
this is not a showstopper to Vista, hereby Vista support is finished!