I posted this last month.
--- Begin Message ---
Hello,
        In case anyone else ever has this problem here is another update.  In
order to make other webapps work correctly (like gridsphere) I added
xercesImpl.jar and xml-apis.jar to the CLASSPATH variable in
catalina.sh.  So all the edits are: remove all -Djava.endorsed.dir
options, and then add xercesImpl.jar and xml-apis.jar to the CLASSPATH
variable.  This make the JVM use it's native xml parsers, but still
makes the apache parsers available to webapps that need them.  Just
putting xercesImpl.jar and xml-apis.jar in the common/lib or shared/lib
dirs didn't work for me (which it seems like it should have).

--Brice



On Thu, 2005-07-21 at 11:32 -0500, Brice Lambi wrote:
> Hello,
>     I came up with a hack that works around my problem.  When you start 
> tomcat catalina.sh starts with the 
> -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed, so if you remove 
> this option (about 7 places in the file) then tomcat will not use the 
> xerces parser, but instead use the native java parsers.  This will 
> probably break any other webapps you have deployed to tomcat, but axis 
> seems unaffected and my web service works. 
> 
> 
> --Brice
> 
> 
> 
> Thorsten Jungblut wrote:
> 
> >Hi,
> >
> >  
> >
> >>Hello,
> >>    I'm having some problems getting a service to run on Axis 1.2.1 (Tomcat
> >>5.0.28, Java 1.5.03, Linux).  I get the following error message:
> >>
> >>java.lang.reflect.InvocationTargetException
> >>        at
> >>org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
> >>        at
> >>org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
> >>        at
> >>org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> >>    
> >>
> >
> >I'm just guessing but afaik, tomcat 5.0.x comes with a xerces 
> >implementation. That implementation is used instead of the one built in 
> >into the jre 1.5.0. While your service is probably built against the 
> >jre-xerces, it may be executed using tomcats xerces.
> >
> >You could try three different things:
> >- remove the xerces implementation from your tomcat (may cause other 
> >problems), should be found at $tomcat_home/common/endorsed
> >- upgrade to tomcat 5.5
> >- avoid using the new features
> >
> >Best regards
> >Thorsten
> >
> >  
> >


--- End Message ---

Reply via email to