Hi, Bertrand Delacretaz schrieb: > (still catching up with my Sling mail ;-) > > Hi, > > On Tue, Mar 17, 2009 at 2:46 PM, Marc Speck <[email protected]> wrote: >> ...You have also my vote if you want to rename >> org.apache.sling.jcr.webdav.impl.servlets.SimpleWebdavServlet. "public class >> SimpleWebDavServlet extends SimpleWebdavServlet" is not very readable and in >> SlingWebDavServlet, there are SimpleWebDavServlet and SimpleWebdavServlet >> that refer to different classes.... > > I agree that this can be confusing, do people agree about renaming the > Sling servlet, to SlingSimpleWebDavServlet, maybe?
Lets see, there are actually two servlets in the jcr/webdav bundle: The SlingWebDavServlet (extends SimpleWebDavServlet) is the one which is registered as a Sling Servlet to handle WebDAV requests to / (root). Whenever the SlingWebDavServlet is getting ready it creates an instance of the (Sling) SimpleWebDavServlet (extends Jackrabbit SimpleWebDavServlet) to handle WebDAV requests at /dav (configurable). This SimpleWebDavServlet is different from the SlingWebDavServlet in that it allows access to all workspaces of the repository. As such the two servlets serve different purposes and cannot (easily) be merged and should also not be merged because we don't want to have a single servlet registered in two locations. So remains the issue of the Sling SimpleWebDavServlet colliding in name with the Jackrabbit SimpleWebDavServlet. I have now issue with renaming this servlet for clarity sake, but SlingWebDavServlet is already taken ;-) We could really name SlingSimpleWebDavServlet to indicate it works the same as the Jackrabbit SimpleWebDavServlet but it is located in Sling. Regards Felix > > -Bertrand >
