if your running jdk 1.4 you should read this

http://xml.apache.org/xalan-j/faq.html#faq-N100C3

-----Original Message-----
From: Donoghue, Mark [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 11:19 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Tomcat 4.1.18, JDK 1.4.1, & Soap--the key issue found!


John,

Good catch!

I wonder what the default parser for your jdk is.  If it's not xerces then I
wonder if setting it to xerces would also fix the problem.  That way you
could stay with the jaxp implementation and not change the default Tomcat
install (which requires you to remember you did so ;-).

-Mark

> -----Original Message-----
> From: J M Craig/Alpha-G [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 20, 2003 12:14 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Tomcat 4.1.18, JDK 1.4.1, & Soap--the key issue found!
> 
> 
> Hi Folks,
> 
> Leaving aside all the fluff RE my malformed server.xml Context entry, 
> there is apparently exactly one problem:
> 
> The full install of Tomcat 4.1.18 includes the following XML 
> Parser JAR:
>     jaxp-parser-impl.jar     (found in $CATALINA_HOME/common/endorsed)
> 
> When I replaced this with the Xerces parser JAR from the Sun Web 
> Services Development Pack
>     jswdp-1_0_01/common/endorsed/xercesImpl.jar
> 
> The Soap server started up happily. :-P (I'm trying not to 
> think about 
> how long this took to figure out!)
> 
> For anyone using the 4.1.18 version of Tomcat, the scripts 
> that drive it 
> are in /usr/bin and have different names than those found in 
> the info on 
> the Jakarta/Tomcat web site and the doc files:
>     dtomcat4    corresponds to     catalina.sh
> 
> I hope this is useful to someone.
> 
> Cheers,
> 
> John
> 
> 


****************************************************************************
This email may contain confidential material.
If you were not an intended recipient, 
please notify the sender and delete all copies.
We may monitor email to and from our network.

****************************************************************************

Reply via email to