glenn 01/03/21 04:36:57
Modified:jasper/src/share/org/apache/jasper Constants.java
Log:
The classpath needed by javac is now built dynamically by using getURLs
on the Context URLClassLoader and all its parent class loaders except
for the system class loader. This removes the
glenn 01/02/08 05:37:08
Modified:jasper/src/share/org/apache/jasper Constants.java
Log:
Put runtime jsp page servlets in a package
Revision ChangesPath
1.8 +5 -0
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/Constants.java
Index: Constants.java
glenn 01/02/03 17:03:18
Modified:jasper/src/share/org/apache/jasper Constants.java
Log:
- Implemented Java SecurityManager
- Switched to using URLClassLoader
Jasper now creates a URLClassLoader for each JSP page and defers any other
class loading to the web app context cl
"Craig R. McClanahan" wrote:
>
> Danno Ferrin wrote:
>
> >
> > I think that keeping the import list to what is required by the spec and
> > refrencing all of the other object we need to compile by the fully
> > qualified name will result in less un-intended colissions.
> >
>
> +1 for importing
Danno Ferrin wrote:
>
> I think that keeping the import list to what is required by the spec and
> refrencing all of the other object we need to compile by the fully
> qualified name will result in less un-intended colissions.
>
+1 for importing exactly, and only, the "default import list" defin
Ok, it's taken me a few days to see this one.
Why does the list saying that an object is used mean it must be
imported? Similarly why shoudlwe import the jasper class when they
could potantially conflict with user imported classes? Why can't we
jsut use the fully qualified name to refrence t
pierred 00/12/08 21:45:48
Modified:jasper/src/share/org/apache/jasper Constants.java
Log:
Cleaned up the default list of imports.
Details (long) below.
The list of "default" imports used in Jasper was as follows
1) default import list as defined in spec (section 2.10.1
