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.
Hey, I think I like the longer version better.
During deploy, we do: - hack web.xml - copy jasper-runtime.jar to /WEB-INF/lib
So we can keep jasper-compiler.jar in /server/lib ?
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
