, 2002 8:00 PM
To: Tomcat Developers List
Subject: RE: Jasper 2 class files
However, in the context of JspC, it's a problem to map them to the same
package and class name. The custom URLClassLoader works within the JSP
engine, but the general servlet class loader doesn't know about those
rules.
So
Is jspcache the place that Tomcat is looking for generated classes? If so,
then the custom JSP classloader is doing its magic.
The java and class files produced by the JspC command line compiler should be
able to be jared up and placed into the WEB-INF directory, like any other
servlet. And
: Wednesday, August 21, 2002 2:56 PM
To: Tomcat Developers List
Subject: Re: Jasper 2 class files
Is jspcache the place that Tomcat is looking for generated classes? If
so,
then the custom JSP classloader is doing its magic.
The java and class files produced by the JspC command line compiler
should
PROTECTED]]
Sent: Wednesday, August 21, 2002 2:56 PM
To: Tomcat Developers List
Subject: Re: Jasper 2 class files
Is jspcache the place that Tomcat is looking for generated classes? If
so,
then the custom JSP classloader is doing its magic.
The java and class files produced by the JspC command
Yes, you can have two JSP pages with the same name but in different directories
and everything will work fine even though they have the same package and class name.
This is because a custom URLClassLoader is created for each individual JSP page.
That class loader only loads the one java class for
,
no matter where they reside, to org.apache.jsp.hello_jsp.
-Original Message-
From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 7:54 PM
To: Tomcat Developers List
Subject: Re: Jasper 2 class files
Yes, you can have two JSP pages with the same name
