|
We have a
product which is using an old version of Xalan 1.2.2. A customer upgraded from java 1.3.1 to 1.4.1_01. Now when they run the software they get
Exception in thread "main" java.lang.NoSuchMethodError: org.apache.xalan.xslt.Process.getDefaultLiaison()Ljava/lang/String; Besides upgrading
to Xalan2 (definitely the correct solution), does anyone know a work around to
this problem? Thanks in
advance … The
complete stack trace is: -- OS:
SunOS 5.6 -- JDK
Version 1.4.0_01 -- Memory:
3149296/3604480 Exception
in thread "main" java.lang.NoSuchMethodError: org.apache.xalan.xslt.Process.getDefaultLiaison()Ljava/lang/String; at
org.apache.xalan.xslt.XSLTEngineImpl.<init>(XSLTEngineImpl.java:367) at
org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(XSLTProcessorFactory.java:79) at
com.ics.SML.SMLpp.processXSL(SMLpp.java:535) *** Error
code 1 At
SMLpp.java:535 is XSLTProcessor
processor = XSLTProcessorFactory.getProcessor(); I opened the xalan.jar file and looked at the Process.class file and it
contains the following: package org.apache.xalan.xslt; // Imports import java.lang.String; import org.xml.sax.SAXException; import java.net.URL; import org.apache.xalan.xslt.res.XSLTErrorResources; public class Process { // Fields private static int
xercesDetected; // Constructors public Process() { } // Methods static { } static String
getDefaultLiaison() { } public static URL
getURLFromString(String p0, String p1) throws SAXException { } public static void
main(String[] p0) { } protected static void
printArgOptions(XSLTErrorResources p0) { } } Linda Derezinski Interface & Control Systems Inc. |
- Re: New Xalan not playing well with Tomcat 4.0? Ushakov, Sergey N
- RE: New Xalan not playing well with Tomcat 4.0? Gary L Peskin
- Re: New Xalan not playing well with Tomcat 4.0? Ushakov, Sergey N
- RE: New Xalan not playing well with Tomcat ... Gary L Peskin
- RE: New Xalan not playing well with Tomcat 4.0? Joseph Kesselman
- Re: Xalan version 1.2.2 with Java 1.4.1_01 java... Linda Derezinski
