> (a) if you're under Tomcat 4.0 AND if you're not using JSP,
> delete crimson.jar from the lib directory. Otherwise the
> version of JAXP 1.1 included will conflict and cause a
> "Sealing violation" SecurityException. This is due to the
> way Sun packaged it--it chokes if a ClassLoader attempts
> to load one of those "sealed" packages from another JAR
Gee, this is pretty disheartening.
Will Xalan 1 work with Tomcat 4? It looks like Xalan 1 will satisfy my
needs.
I'm going to have to use xerces and xalan because of project requirements,
and was looking at setting up a doFilter on JSPs or using the XML taglib to
allow me to translate the XML output into HTML, all in the way a Sun
whitepaper describes (http://java.sun.com/products/jsp/pdf/JSPXML.pdf,
starting on page 8, and especially the Figure 3 on page 10).
Is this incompatibility between the two apache projects Tomcat 4 and Xalan 2
considered a bug by either project?
dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
