Hi Robert, Thanks for your answers. I have investigated your suggestions and here are my findings: 1) Under windows, it is not possible to create a symbolic link to a WebDAV drive, even when it is mounted as a drive using Novell NetDrive. Symbolic linking is available for NTFS volumes only. 2 and 3) In both scenarios, URLs are still served by Slide and therefore JSPs will be handled by the Slide servlet and not the JSP servlet. This makes sense because the only way that the BIND will work is if the WebDAV server handles the URL! Additionally, PUTting the content to a different path still implies that the PUT must be handled by WebDAV - again, this rules out the JSP Servlet. I think what is required is a re-implementation of the default and JSP servlets bundled with Tomcat to allow serving of content from a WebDAV repository - or the creation of a Filter in front of the WebDAV that will execute and compile JSPs (not sure if this is possible at all - again, how will you know whether a request is to edit the JSP or execute it?). Historically, Tomcat used to allow the creation of contexts in Server.xml like this: <Context docBase='http://server' path='/test' .... /> This would do the trick but is not allowed in versions after Tomcat 3. Does anyone know of a way that JSP content can be executed from a WebDAV repository (be it slide or any other)? Kind regards, Patrick
________________________________ From: Robert r. Sanders [mailto:[EMAIL PROTECTED] Sent: Mon 07/02/2005 14:24 To: Slide Users Mailing List Subject: Re: Serving slide content from another webapp I'm not an expert but it seems to me that you have a couple of potential options: 1. Use a 'nix style link on the server-side to map two paths - one of which is served by the Slide WebDAV servlet, the other of which is mapped to the JSP servlet. 2. Add a hook so that when a file is successfully 'PUT' slide also copies it to a path where it can act as a JSP. 3. A little more complex to implement but maybe a better fit: I've yet to try it, but slide has support for the WebDAV BIND spec which should allow you to map more than one URL to the same content, you might be able to use this to map a 'readable' and an 'executable' path to your JSPs. Patrick van Kann wrote: >Hello, > >I have a requirement that means developers need to be able to edit JSP files >(i.e. get and put from a WebDAV-aware IDE) on a Slide WebDAV server. I >understand that this requires the disabling of the JSP servlet for the Slide >app (otherwise it intercepts puts and gets before the WebDAV servlet gets them) > >However, I need to be able to execute the JSP files from a browser or IDE >during development (round-tripping), and also provide a "public" website that >allows non-developer users to access the JSPs. > >Is it possible to create a new "read-only" webapp that serves content from the >same Slide repository as my Slide webapp (without being Slide/WebDAV enabled)? >For example, it seems that Cocoon has a module that uses the "slide://" prefix >to access a slide domain's content - is there anything like this available for >non-Cocoon apps? > >Thanks in advance, > >Patrick > > > -- Robert r. Sanders Chief Technologist iPOV www.ipov.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
