At 12:09 PM 7/16/2001 -0600, Liaw, Wan-Bih wrote:

>SOAP works fine, but something it calls on isn't there.
>    (a) what's your server setup? Tomcat, WebLogic, Jrun, &c&c&c?
>
>
>    WebSphere 3.5 AE with Fixpack 3.5.3
>    IBM HTTP Server 3.12.1


aha, WebSphere. In the docs, you'll find

   soap-2_2\docs\install\websphere.html which says, among other things

>IMPORTANT: WebSphere comes with an XML parser (WebSphere\AppServer\lib\xml4j.jar) 
>which uses DOM level 1 interfaces. Even if you put the Xerces 1.1.2's (or later) 
>xerces.jar in your classpath, the wrong interfaces are found by any Java code running 
>in WebSphere because WebSphere puts the user's classpath at the end. So, you must 
>edit WebSphere\AppServer\bin\admin.config file and put xerces.jar at the BEGINNING of 
>the com.ibm.ejs.sm.adminserver.classpath= variable 

It says other things which you've presumably got to read, but I
think the problem here is that you are running a DOM 1 parser
underneath SOAP. Hope this helps...

Tom Myers


>    (b) what happens when you look at 
><http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter ?
>(for me, that's 
><http://localhost:8080/soap/servlet/rpcrouter>http://localhost:8080/soap/servlet/rpcrouter
> and it says
>"Sorry, I don't speak via HTTP GET- you have to use HTTP POST to talk to me."
>which is the right thing for it to say)
>
>This works -- I got the same result.
>
>
>   (c) what's your client classpath? It looks like things are blowing up as you run
> >java org.apache.soap.server.ServiceManagerClient 
><http://localhost:8080/soap/servlet/rpcrouter>http://localhost:8080/soap/servlet/rpcrouter
> deploy DeploymentDescriptor.xml
>(that's the line within testit that seems to be blowing up for you)
>so that's using your default system classpath, and of course it also
>uses your JAVA_HOME /jre/lib/ext
>
>Classpath for both client and server: 
>D:\WebSphere\AppServer\lib\xerces.jar;D:\WebSphere\AppServer\jdk\jre\lib\rt.jar;D:\WebSphere\AppServer\lib\ejs.jar;D:\WebSphere\AppServer\lib\ujc.jar;D:\WebSphere\AppServer\lib\servlet.jar;C:\soap-2_2\lib\soap.jar;C:\RhinoTools\jstools.jar;C:\j2sdkee1.3\lib\j2ee.jar;.
>  
>JAVA_HOME:
>D:\WebSphere\AppServer
>
>
>   (d) what's your server classpath?
>
>Please see (c)
>
>
>   (e) what jars are in your JAVA_HOME /jre/lib/ext and especially which of
>them contain the uncompressed string
>    org/xml/sax/helpers/AttributesImpl
>(use grep, or ^F for windows)
>
>It has to be D:\WebSphere\AppServer\jdk\jre\lib, in Websphere.
>
>D:\WebSphere\AppServer\jdk\jre\lib>dir/w *.jar
>  Volume in drive D has no label.
>  Volume Serial Number is 6CE0-69FD
>
>  Directory of D:\WebSphere\AppServer\jdk\jre\lib
>
>i18n.jar   jaws.jar   rt.jar
>                3 File(s)     15,174,893 bytes
>                           1,085,247,488 bytes free
>
>
>-----Original Message-----
>From: Tom Myers [<mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]]
>Sent: Monday, July 16, 2001 11:01 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: RE: When to use SOAP?
>
>
>At 09:56 AM 7/16/2001 -0600, Liaw, Wan-Bih wrote:
>
> >I have made sure I following eth instructions in  
><<http://xml.apache.org/soap/faq/faq_chawke.html#Q1_4>http://xml.apache.org/soap/faq/faq_chawke.html#Q1_4>http://xml.apache.org/soap/faq/faq_chawke.html#Q1_4
> and still got the following error when I run it:
> >
> >C:\soap-2_2\samples\addressbook>testit
> >This test assumes a server URL of 
><<http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter
> >Deploying the addressbook service...
> >Ouch, the call failed:
> >   Fault Code   = SOAP-ENV:Server.Exception:
> >   Fault String = org.xml.sax.helpers.AttributesImpl: method getQName(I)Ljava/lan
> >g/String; not found
> >.
> >
> >Does Apache Soap really work???
>
>SOAP works fine, but something it calls on isn't there.
>    (a) what's your server setup? Tomcat, WebLogic, Jrun, &c&c&c?
>    (b) what happens when you look at 
><http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter ?
>(for me, that's 
><http://localhost:8080/soap/servlet/rpcrouter>http://localhost:8080/soap/servlet/rpcrouter
> and it says
>"Sorry, I don't speak via HTTP GET- you have to use HTTP POST to talk to me."
>which is the right thing for it to say)
>   (c) what's your client classpath? It looks like things are blowing up as you run
> >java org.apache.soap.server.ServiceManagerClient 
><http://localhost:8080/soap/servlet/rpcrouter>http://localhost:8080/soap/servlet/rpcrouter
> deploy DeploymentDescriptor.xml
>(that's the line within testit that seems to be blowing up for you)
>so that's using your default system classpath, and of course it also
>uses your JAVA_HOME /jre/lib/ext
>   (d) what's your server classpath?
>   (e) what jars are in your JAVA_HOME /jre/lib/ext and especially which of
>them contain the uncompressed string
>    org/xml/sax/helpers/AttributesImpl
>(use grep, or ^F for windows)
>
>Tom Myers
>
>
>
> >-----Original Message-----
> >From: Tom Myers 
>[<<mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]]
> >Sent: Friday, July 13, 2001 6:31 PM
> >To: [EMAIL PROTECTED]
> >Cc: [EMAIL PROTECTED]
> >Subject: RE: When to use SOAP?
> >
> >
> >At 02:51 PM 7/13/2001 -0600, Liaw, Wan-Bih wrote:
> >
> > >Ok, I just tested the first sample in soap-2_2, and got the following error. 
>Anyone can help me?   Thanks!
> > >
> > >C:\soap-2_2\samples\addressbook>testit
> > >This test assumes a server URL of 
><<<http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter>http://localhost:80/soap/rpcrouter
> > >Deploying the addressbook service...
> > >Ouch, the call failed:
> > >   Fault Code   = SOAP-ENV:Server.Exception:
> > >   Fault String = org.xml.sax.helpers.AttributesImpl: method 
>getQName(I)Ljava/lang/String; not found
> >
> >I'd expect this to be a variant on
> >    
><<http://xml.apache.org/soap/faq/faq_chawke.html#Q1_4>http://xml.apache.org/soap/faq/faq_chawke.html#Q1_4>http://xml.apache.org/soap/faq/faq_chawke.html#Q1_4
>  or of course #Q1_5
> >'cos it certainly sounds like an out-of-date parser has gotten hold of this;
> >getQName in that package was once called getRawName
> >(see 
><<http://www.megginson.com/SAX/Java/changes.html>http://www.megginson.com/SAX/Java/changes.html>http://www.megginson.com/SAX/Java/changes.html
> )
> >Or then again, it might be something totally Other.
> >
> >Tom Myers

Reply via email to