The fist solution adds protocol specific code to the low level service (when you add
a new frontend ex JNDI/SOAP, you have to change the low level service)
The second solution adds low level exception tests to the protocol level (when you
get a new nested exception from a new store you have to ch
I understand your argumentation, but wouldn't the change you propose "infect"
the core API with specifics of the WebDAV protocol (or with HTTP transport in
general) ?
One alternative that I see:
There are already exceptions in Slide that pretty much directly match the
various HTTP/WebDAV resp
Hi all,
Our child store wants/needs more control over the generated response codes.
Currently the child stores may either throw a ServiceAccessexception, which
is mostly transformed into an "Internal Server Error" and some more specific
Exceptions, which are transformed by a method-specific algor
juergen 01/07/19 04:10:59
Modified:src/webdav/server/org/apache/slide/webdav/method
DeleteMethod.java MkcolMethod.java MoveMethod.java
PropPatchMethod.java PutMethod.java
UnlockMethod.java
Log:
in case of an err