Hi Jan,
> > Under tomcat 3.2.1, a request for "blah/" generates a 302 redirect to
> (also 3.3m2)
> > "blah/index.jsp" rather than just serving up the content of index.jsp!
> Currently, it appears that if I wish to avoid broadcasting my use of
> JSPs, I've just got to code servlets and use those instead. This isn't
> particularly satisfactory.
Use web.xml to define mappings. You can associate any name to any .jsp
file.
> I know everyone's (justly) proud of tomcat, but there's no need to ram
> the implementation mechanisms for a website down people's throats.
This isn't the reason - I just wanted to make sure everything works and
we avoid some bugs ( which is quite important ). This is the cleanest
solution ( as oposed to some dirty hacks in 3.1 - which resulted in quite
a few bugs ).
The real problem was the communication between jasper and tomcat, and most
of this is resolved in 3.3 ( in JspInterceptor - but we still support
JspServlet ).
> What's the likelihood of revising this decision?
Likely - after we finish refactoring jasper or if we have too much free
time or if you send a patch ( after running all watchdog and sanity
tests ! ). ( but even in that case, this will be an optional thing you can
specify in your server.xml, with the current behavior as default )
Costin
