Julian Reschke wrote:
That problem will not go away, unless the server finds a way to simulate the expected WebDAV behavior. Maybe we should consider lock time out handling for JCR 2.0, after all?
with JSR170 lock timeouts are left to the implementation and if i remember correctly this hasn't change for 283. from my point of view it would be desirable if jackrabbit had some built-in timeout mechanism or at least would allow the to configure it. currently it's really a hack to get rid of a open-scoped lock once the token has been lost. regards angela
