The main point is to _not_ hack anything, but just use the standard. If you precompile your app - and include jasper-runtime.jar in WEB-INF/lib - the result should work in _any_ container - the precompiled jsps are _just_ regular servlets that happen to use a lib and extend from a base class. That used to work - I haven't tested it recently but it should still work.
The result of precompilation must remain a webapplication that is not specific to tomcat ( or worse - to a specific version of tomcat, as would be the case here, I assume such a change won't be backported to 4.0 !). We have a standard way to declare the servlets that result from jsp precompile, we have a standard way to declare the mappings - and I see no good reason to invent another mechanism to do this. I don't like web.xml - and in 2.4 is even worse than it ever was ( with the XML Schema it enters a whole new level of complexity and uglyness). However it is good enough for this use case - and it is the standard. Costin Tim Funk wrote: > Could an alternate hack be to modify JspServlet to allow an additional > init parameter which would be the file which contains the mapping of the > precompiled jsp's? The config file could just be the web.xml snippet > generated by the precompilation process. This way web.xml isn't touched > and if Jasper is used in another container, then all is OK? > > > -Tim > > > Bill Barker wrote: >> I think that parsing two web.xml files is plenty. There is no reason to >> add >> a third. Also, since it is possible to use Jasper with other containers, >> adding a non-standard feature like this makes that harder to do. >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
