Hi all, I got this error when I tried to start my WAS 3.5. I don't understand what it means I hope someone out there can help me out with this problem java.lang.NoSuchMethodError: org.xml.sax.Attributes: method getQName(I)Ljava/lang/String; not found at org.apache.crimson.tree.AttributeSet.<init>(AttributeSet.java:139) at org.apache.crimson.tree.XmlDocumentBuilder.startElement(XmlDocumentBuilder.java:463) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1449) at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:179) at javax.xml.parsers.DocumentBuilder.parser
Thanks [ May 29, 2002: Message edited by: wanrazali ]
Have you put any xml parsers or related jars anywhere? e.g. added one to the classpath of an application, appserver or websphere itself? This error could be the result of some code expecting to find one version of some api but getting another.
check this article out : 6- Xalan and Xerces - Not just for the Ancient Greeks anymore --------------------------------------------------------------------- One of the more common questions that we hear in WebSphere support is, "How do I setup WebSphere to use the Xerces.jar and Xalan.jar that is distributed with Apache rather than using the Xerces.jar and Xalan.jar that is is distributed with WebSphere?" For quite some time, the answer was, "You can't do that." The problem was that the Adminserver required the use of WebSphere's Xalan and Xerces files. But your voices have been heard and there is now an approved method for using Apache-based Xalan and Xerces files in WebSphere Application Server V3.5.3. E-fix PQ47050 resolves your problem if properly applied and if used in conjunction with inserting the correct classpath statement for each application server. The e-fix can be downloaded from http://www.ibm.com/software/webservers/appserv/efix.html
You also need to add the following string to the command line arguments for each application server using xalan and xerces: -classpath ....:xxx/xalan.jar:xxx/xerces.jar... Substitute the directory where you have stored the jars for the xxx. If you are using Windows NT then use semi-colons instead of colons. Restart the server so that the classpath takes effect.
Forget Steve. Look at this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop