Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem while running SOAP code

5 views
Skip to first unread message

Brian Ortner

unread,
Apr 21, 2001, 4:27:34 PM4/21/01
to
I've gone through the newgroup and tried the placing of the xerces.jar file
at the head of the classpath both in the admin.config classpath and in the
application server classpath. In both cases I continue to receive the
following error:

Error Message: Server caught unhandled exception from servlet [Main]:
org.w3c.dom.Node: method getNamespaceURI()Ljava/lang/String; not found
Error Code: 500
Target Servlet: Main
Error Stack:

----------------------------------------------------------------------------
----
Root Error-1: org.w3c.dom.Node: method getNamespaceURI()Ljava/lang/String;
not found

java.lang.NoSuchMethodError: org.w3c.dom.Node: method
getNamespaceURI()Ljava/lang/String; not found
at org.apache.soap.util.xml.QName.<init>(QName.java:80)
at org.apache.soap.util.xml.QName.matches(QName.java:146)
at org.apache.soap.Envelope.unmarshall(Compiled Code)

I looked at the xml4j.jar and the org.w3c.dom.Node doesn't have the method,
but the xerces
does.
I ran both admin and the app server with verbose on but still did not see
anything that would help.
I even tried un-jaring the xml4j.jar extracting the org.w3c directory and
re-jaring it but I still
had the same problem.
I had the same error message while testing in JBuilder with Tomcat, but when
I placed the xerces.jar
infront of the tomcat xml.jar file it began to work.
I'm afraid I'm out of directions to pursue. Does anyone have any
suggestions?
thanks

b

JJ

unread,
Apr 23, 2001, 6:32:27 AM4/23/01
to
Our WebSphere administrators had to put all SOAP related JARs in
admin.config. Then don't forget to restart the whole WebSphere (not only the
application server) to allow WAS to update its classpath.
(We are using Apache SOAP.)

This is NOT good because if we would have multiple application servers and
such restart would affect every application server.

This behaviour seems to differ between WAS Advanced NT and Solaris.
How can this be solved in a better way?

Maybe some IBM staff could comment this.

--
Best regards

Joacim Jarkeborn
IT Consultant - Systems Development
Gothenburg, Sweden


"Brian Ortner" <bor...@us.checkpoint.com> wrote in message
news:9bsna5$cum$1...@news.boulder.ibm.com...

0 new messages