From: Alessandro Ronchi [mailto:[EMAIL PROTECTED] > Here is my example: > I have a context named "dwers", and I correctly execute this jsp page: > http://localhost:8080/dwers/index.jsp > located on > /usr/share/tomcat/webapps/dwers/index.jsp > > what's the correct webdav url?
All tomcat responses are provided by servlets. Each request is handled by one, and only one servlet. The servlet that is used is controlled by the servlet mappings. There are some default ones in conf/web.xml and you can specify applciatio specific ones in WEB-INF/web.xml. The rules that control the mapping are defined in the servlet spec. The JSP and sevrlet specs are a must read for any web developer. How does all of this affect you? Well, to view a JSP .jsp files must be mapped to the JSP servlet but to edit them they must be mapped to the webdav servlet. A resource will only ever be mapped to a single servlet. Webdav isn't intended to provide inplace editing of web application files. So, how can you get around this? - Use an IDE that lets you edit the JSP locally and deploys it automatically. I use Eclipse and the MyEclipse plugin but there are plenty of other options out there. - Edit you JSPs locally and use ant to deploy. - If you have access to the machine running tomcat (either directly or via putty etc) just edit the JSPs directly in the tomcat directory - Create a second context with the web.xml setup for webdav (use a /* mapping) and a symbolic link to the files in the 'normal' app - I don't know unix very well so can't really explain how to set something like this up HTH Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
