Hi Larry,
I'm +1 on implementing your changes - setting options for jsp is very
important ( I use jikes most of the time ).
Setting jasper options in web.xml has many problems, and I don't think we
should do it.
I agree adding a ContextManager/Context property is the best solution for
3.2 - mi
> My preference would be to set the options on JspInterceptor, using the
> server.xml format.
> Context and ContextManager shouldn't know/care about what happens in
> interceptors unless it's absolutely needed. I think the biggest
> priority
> right now is to make sure all 9 core objects a
> For Tomcat 3.3
>
> In Tomcat 3.3, I could apply the jasper changes for compatibility. However,
> JSP compilation occurs differently. Instead of using a JSP servlet, it
> uses an interceptor that calls Jasper with its own options and then
> calls the compiler itself. Thus, any options string
Hi,
To add the ability to compile JSP's with debugging information and
achieve more flexible control of Jasper, I propose the following:
For Tomcat 3.2M1
1) Add a "debugInfo" property to Options.java and
EmbeddedServletOptions.java. The default value is false.
2) Update EmbeddedServletOpti
