|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] David, Gave this a try this AM and it did not work. The server will not start with the XML parser JAR files moved from common/endorsed to the server/lib folder. I receive the following error immediately on startup. Exception during startup processing java.lang.reflect.InvocationTargetException: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:141) at org.apache.commons.digester.Digester.getFactory(Digester.java:511) At this point it is starting to look like my best bet will be waiting for the next version of jtopen unless you think an older rev of Tomcat might work better? Thanks Mark "David Morris" <David.Morris@plumcreek.com> Sent by: java400-l-admin@midrange.com 11/08/2002 06:26 PM Please respond to java400-l To: <java400-l@midrange.com> cc: Subject: Re: AS/400 and Java (Tomcat on AS400) 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 _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
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.