Rickard �berg writes:
> Hi!
>
> Tom Cook wrote:
> > This could be one of my servlets needing this, I guess (we've been
> > running it in stand-alone tomcat with all the lib stuff in
> > $TOMCAT-HOME/lib. The SAXParserFactory class in definitely in
> > xerces.jar in lib/ext. Is there some reason why EmbeddedTomcatService
> > and my contexts can't see these classes?
>
> Probably a classloader issue. Are the Tomcat classes added to the
> CLASSPATH env variable prior to jBoss startup? But not the SAX stuff?
> Because then Tomcat won't see it I think due to normal classloader
> behaviour.
Yes, the tomcat stuff is added in run.sh.
> If this is the case, then as before I think the solution is to add the
> Tomcat classes through the ClassPathExtension mechanism. That is much
> cleaner and should ensure proper operation.
Adding xerces.jar to the classpath before startup fixed that problem,
but made a new one. In our servlet we use
org.w3c.dom.Document.getElementById to find an element with a specific
id. Now this method exists on the org.w3c.dom.Document in xerces.jar
but not on the one in xml.jar which comes with jboss! Needless to
say, this caused some problems. I fixed it (sort of) by:
mkdir xmltemp
cd xmltemp
jar -xf ../xml.jar
jar -xf ../ext/xerces.jar
jar -cf ../xml.jar *
which works, but is messy as. Why are the two doms different?
Tom
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
