Scott Stirling wrote:
>
> I agree with Craig.
>
> The ability to run JSP apps without any source JSPs must be maintained
> for app vendors who want to ship without source code. Not sure if this
> patch would interfere with that or not.
It shouldn't; if you want to distribute JSP pages without source,
you compile them to servlet classes and add mappings for the
paths to the servlets in web.xml. The spec may be vague on this,
but that's still what I believe is the recommendation stated in
the section about precompilation.
> A separate issue: if a user removes the source JSP, it may be OK to
> remove the JSP class file, but what about the class loaded in memory
> (assuming the server was running when the JSP was deleted)? To be
> consistent you would have to unload that JSP class,
Not necessarily unload, but remove all internal (automatic) mappings
so that a request for the JSP always results in a 404.
> and possibly any
> associated objects (depending how JavaBeans and JSP are loaded in
> classloaders in Tomcat). For example, if an application scope bean were
> loaded by that JSP, would that bean be dumped with the classloader for
> that JSP or not?
Hmmm... I think that's overkill.
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
