Hi, I somewhat solved the problem by removing xercesImpl.jar from my CLASSPATH in that Xalan now works as expected. I still have xerces.jar in my classpath but it is named "z_xerces.jar" so it will be picked up later than xercesImpl.
I was of the notion that xercesImpl was of the newer xerces and that xalan worked with it? I continued to go through the jar files one by one after discovering this (swapping them in and out) and after removing z_xerces.jar I received this error: (Location of error unknown)XSLT Error \ (java.lang.NoClassDefFoundError): \ org/apache/xerces/framework/XMLParser Perhaps xalan is trying to use the older Xerces? For the time being I'll just swap out xercesImpl.jar when working with Xalan, but any insight into this would be most apprectiated. Regards, Elizabeth Elizabeth Barham <[EMAIL PROTECTED]> writes: > Hi, > > I installed soap.jar on my system (and all it's dependencies) to play > with it. After installing these jar files (activation.jar, ant.jar, > ejb.jar, imap.jar, java_cup.jar [?], jcert.jar, jnet.jar, jsse.jar, > smtp.jar, pop3.jar, mail.jar, maybe a few more) I receive this error: > > [EMAIL PROTECTED] java org.apache.xalan.xslt.Process -in job-listing.xml \ > -xsl job-listing.xsl > > (Location of error unknown)XSLT Error (java.lang.VerifyError): (class: \ > org/apache/xml/dtm/ref/IncrementalSAXSource_Xerces, method: startParse \ > signature: (Lorg/xml/sax/InputSource;)V) Incompatible object argument \ > for function call > > Has anyone seen this before or know how to determine the cause of this > error?
