Hi, in general I think it is much simpler to have nodes for each user in the main workspace (eg. /home/userX) than to create a new workspace for each user. I think that solution won't scale well.
Regarding Windows web folders: AFAIK that one is buggy as hell and not so conformant to the spec. I would try a different webdav client tool for Windows. I looked at the code and I don't see any direct errors (see below for a comment). But I wonder how the login page interacts with the Webdav access? Is the user required to login first via a browser, then his workspace gets created if it doesn't exist yet and then he switches over to Webdav to do his work? Do you supply the username/workspace name in the webdav url (which by default is sth like /repository/<workspace-name>/<repo-path>)? On Thu, Jan 29, 2009 at 6:17 AM, imadhusudhanan <[email protected]> wrote: > String enableToUser = request.getParameter("user"); > if(enableToUser != null && !enableToUser.equalsIgnoreCase("")) { > WebDAVServlet webdavServlet = new WebDAVServlet(); > Repository repoCreated = webdavServlet.getRepository(); Creating a new WebdavServlet every time only to get the repository from its configuration is overkill. You should rather use JNDI for that (or at least a global singleton). This could also be the reason for errors, but I don't know what happens in the internals of the webdavservlet code. Regards, Alex -- Alexander Klimetschek [email protected]
