Glenn Nielsen wrote:
>
> Here is my proposal for implementing the Java SecurityManager in Tocmat 4.
> Work on implementing this proposal is in progress. Comments please?
>
> Tomcat 4 Java SecurityManager Proposal
>
> Tomcat 4 will require the Java SecurityManager, use of the
> SecurityManager will be optional when Tomcat is embedded in
> another application.
> [...]
-0. Why not make it optional for standard use as well? If I use Tomcat
for development only, I'm not concerned with security and don't
want to mess with policy files.
> [...]
> Jasper JSP class loading
> ------------------------
>
> Jasper will have the old 1.1 compatability code stripped out.
+1
> The work directory will be moved inside the web application context
> /WEB-INF/ directory. [...]
-1. It should be possible to configure Tomcat so that the work
directory is located under /tmp, or any other standard OS location
for temporary files. Besides, creating files under /WEB-INF will
not work if we one day support running applications straight from
the WAR file.
> Jasper will be modified so that each individual jsp page
> will have its own URLClassLoader. When each jsp page has
> its own URLClassLoader we can remove the need to munge and version
> the jsp java and class file names. We can also create directory
> paths in the work dir for the context that matches the jsp page
> path in the context. This will make it easier to view the
> generated source for a jsp page. When a jsp page is recompiled,
> a new instance of the URLClassLoader for that page will be
> created. [...]
+1. Great!
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]
