Sam Ruby wrote:
> Craig R. McClanahan wrote:
> >
> > NOTE: According to Ed Goei, Xerces is, or very soon will be,
> > JAXP 1.1 compatible, so you will be able to use it (instead
> > of Crimson) even in an environment that needs Jasper.
>
> Unless Jasper does some wierd reflection tricks that I'm not aware of, I've
> been successfully compiling all versions of Tomcat against the latest
> Xerces for quite some time. For example:
>
>
>http://oss.software.ibm.com/developerworks/opensource/jakarta/proto2/jakarta-tomcat-4.0.html
>
> - Sam Ruby
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/[email protected]/>
> List Help?: [EMAIL PROTECTED]
It seems to be more of a run-time issue versus a compile time
issue. The problem appears to be around how Tomcat4/Catalina
searches the CLASSPATH and resolves the XML parser classes
differently than Tomcat3.2 ie- jetspeed will build fine and resolve
the libraries needed to compile, but the error does not surface until you
start jetspeed up and point your browser at the main page.
There are several messages on the tomcat list that seem related.
It could be how Tomcat4 + the TDK uses jaxp/crimson vs the version
of xalan/xerces that Jetspeed is using.
The message that I found on the tomcat list was:
http://www.mail-archive.com/[email protected]/msg09193.html
I am experimenting with various versions of xalan/xerces/jaxp to try
to narrow down the problem...
-bill
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
