× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mark

Did you try moving the xercesImpl and xml-apis jar files out of
common/endorsed/lib to
server/lib? That should make them invisible to your apps. Does this
happen on a
windows based machine also? I can't remember the exact circumstances
but I have
seen the verify error in other cases. I believe it was when compiling
with the 1.4 JDK
with a 1.3 target and deploying to the 400. In that case, compiling
with the 1.3 JDK
fixed the problem.

David

>>> MarkP@softlanding.com 11/08/02 01:50PM >>>
This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
David,

With x4j400.jar in my webapp/lib folder I get this error:

java.lang.VerifyError: (class: com/ibm/as400/data/PcmlSAXParser,
method:
signature: (Ljava/lang/String;Ljava/lang/ClassLoader;)V) Incompatible
object argument for function call
        at
com.ibm.as400.data.ProgramCallDocument.loadSourcePcmlDocument(ProgramCallDocument.java:1044)
        at
com.ibm.as400.data.ProgramCallDocument.loadPcmlDocument(ProgramCallDocument.java:949)
        at
com.ibm.as400.data.ProgramCallDocument.(ProgramCallDocument.java:97)

Which I assume has to do with Xerces issues.

If nothing else, apparently it is the next version of jtopen (3.3) due
in
a week or so that is supposed to change it to work with newer parsers.
Hopefully that will resolve it.

Mark


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.