> The Jasper page compiler needs to have access to all of the bean classes
> that you might have placed in WEB-INF/classes and WEB-INF/lib. This could
> be "faked" by setting up yet another class loader that simulates the
> "real" webapp class loader (in terms of what repositories it gives you
>
> I'm interested in seeing if we can gather enough folks to start a "Jasper
> 2.0" effort, on a completely fresh slate. The design of this would take
> into account the two input syntaxes and everything we've learned, and the
> implementation could implement many obvious optimizations that would
On Sat, 24 Mar 2001, Kevin Jones wrote:
> Craig,
>
> bear with my ignorance of how Catalina works at this point.
> I'm assuming that the JSP servlet compiles the 'raw' JSP->XML->Java and then
> compiles this to a .class file.
>
It doesn't actually go to XML if the original syntax was the JSP
Craig,
bear with my ignorance of how Catalina works at this point.
I'm assuming that the JSP servlet compiles the 'raw' JSP->XML->Java and then
compiles this to a .class file.
Why does the Jasper class-loader delegate to the web-apps classloader, isn't
the Jasper step entirely independent. If so
Kevin Jones wrote:
> > It (the JSP servlet) is loaded early already.
> >
> > It (and its XML parser) are now loaded by another classloader (not sure
> > that was
> > true on the 22nd -- if your Tomcat 4.0 has "jasper-compiler.jar" and
> > "jasper-runtime.jar" separated, then it is for you).
>
> I
> It (the JSP servlet) is loaded early already.
>
> It (and its XML parser) are now loaded by another classloader (not sure
> that was
> true on the 22nd -- if your Tomcat 4.0 has "jasper-compiler.jar" and
> "jasper-runtime.jar" separated, then it is for you).
I have jasper-compiler.jar in 'jaspe
Kevin Jones wrote:
> Yep 1.3
>
> > I think the only workaround for this is to ship our own copy of
> > the JAXP JAR
> > files, with the "sealed" attribute removed. I'm also going to be
> > talking with
> > the JAXP folks about removing that in their next release.
>
> :-(
>
> What would happen if
made a special case of the JSP servlet and loaded
it early?
Could you preload jasper somewhere else?
Kevin Jones
DevelopMentor
www.develop.com
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: 23 March 2001 19:05
> To: Kevin Jones
> Cc: Tom
Kevin Jones wrote:
> Craig,
>
> I'm playing with the 22nd March drop of Catalina, and I've come across a
> scenario where the new classloading architecture doesn't quite work.
>
> I'm using Xerces and Xalan (although Xalan is irrelevant to this). If I
> access a servlet that uses XML and I don't
Craig,
I'm playing with the 22nd March drop of Catalina, and I've come across a
scenario where the new classloading architecture doesn't quite work.
I'm using Xerces and Xalan (although Xalan is irrelevant to this). If I
access a servlet that uses XML and I don't put Xerces in my
web-app/myapp/l
10 matches
Mail list logo
