> Hello
>
> How can I upload JSPs?
>
> Here is part from my log:
> 2001-06-17 06:03:56 - ContextManager: SimpleMapper1: Default map
> /files/snoop.jsp null
> 2001-06-17 06:03:56 - ContextManager: SM: Extension match /slide
> /files/snoop.jsp .jsp
> 2001-06-17 06:03:56 - ContextManager: SimpleMapper1: SM: Found extension
> mapping jsp(org.apache.jasper.servlet.JspServlet/null)...
>
> I don't have *.jsp mapping in my web.xml but it comes from the Tomcat...
>
> But anyway, the problem is more bigger. It means if I have some mapping
> in my web.xml file - it looks like I can't upload these files...
>
> I'm using SimpleMapper1. Should I use something different?
Tomcat has the annoying tendency to add the default mappings. The latest
versions of Tomcat 3.x don't have the problem, according to Costin.
I ran into the issue when I did some integration work with Catalina, and I
ended up writing some code to remove all non-Slide related mappings so that
it's actually possible to manipulate *.jsp files (there was also a problem
with *.shtml).
I don't think it's possible to achive the level of integration you may want
with Tomcat 3.x with Slide (ie, uploading the JSP, and then running it with
Jasper), because Tomcat 3.x is designed only to run off the filesystem. Of
course, with the appropriate stores, it's possible to get Slide to
manipulate files.
You may want to check out the Tomcat 4 based binaries built using the
catalina-dist target, and which allows to have web applications running off
a Slide namespace (one web application is mapped to one Slide namespace).
This is still an early build, but I think it gives a good idea at the level
of integration which will be achived.
Remy
