You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Tim Good <ts...@verizon.net> on 2001/05/24 04:57:12 UTC

RE: Installation Wall--continued

Sanjiva,

Using tomcat 3.2.1; switched to soap v2.2 rc1 per your suggestion; NT Server
4.0 (SP4 I believe); xerces 1.3.0.

Here is the 8989 view using tunnelGUI:

POST /soap/servlet/rpcrouter HTTP/1.0Host: localhost:8989Content-Type:
text/xml; charset=utf-8Content-Length: 2972SOAPAction: ""<?xml version='1.0'
encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><ns1:deploy
xmlns:ns1="urn:xml-soap-service-management-service"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><descript
or xmlns:ns2="http://xml.apache.org/xml-soap"
xsi:type="ns2:DeploymentDescriptor"><faultListener
xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:Array"
ns3:arrayType="xsd:string[1]"><item
xsi:type="xsd:string">org.apache.soap.server.DOMFaultListener</item></faultL
istener><providerClass
xsi:type="xsd:string">samples.addressbook.AddressBook</providerClass><servic
eType xsi:type="xsd:int">0</serviceType><serviceClass xsi:type="xsd:string"
xsi:null="true"/><methods
xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:Array"
ns4:arrayType="xsd:string[4]"><item xsi:type="

Here is the 8080 view:

HTTP/1.0 404 Not FoundContent-Type: text/htmlContent-Length:
193Servlet-Engine: Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java
1.3.0; Windows NT 4.0 x86; java.vendor=Sun Microsystems
Inc.)<head><title>Not Found (404)</title></head><body><h1>Not Found
(404)</h1><b>Original request:</b> /soap/servlet/rpcrouter<br><br><b>Not
found request:</b> /soap/servlet/rpcrouter</body>

Here is what appeared in the Tomcat window:

[Time] - Ctx( /soap ): 404 R( /soap + /servlet/rpcrouter + null) null

I'm stumped and have not had time yet to perform lower level tracing that
Tom suggests in his previous posts.

Tim


-----Original Message-----
From: soap-user-return-7732-ts.good=verizon.net@xml.apache.org
[mailto:soap-user-return-7732-ts.good=verizon.net@xml.apache.org]On
Behalf Of Sanjiva Weerawarana
Sent: Tuesday, May 22, 2001 5:23 PM
To: soap-user@xml.apache.org; ts.good@verizon.net
Subject: Re: Installation Wall--didn't show you all of string



Are you using v2.2 RC1? If not can you please try that?

If you are, then can you please post your config info (OS, servlet
container etc.).

Thanks,

Sanjiva.

----- Original Message -----
From: "Tim Good" <ts...@verizon.net>
To: <so...@xml.apache.org>
Sent: Tuesday, May 22, 2001 11:12 AM
Subject: RE: Installation Wall--didn't show you all of string


> What I've discovered this morning.
>
> I restarted tunnel and tried to deploy.  The first time, the 8989 is
longer:
>
> POST /soap/servlet/rpcrouter HTTP/1.0Host: localhost:8989Content-Type:
> text/xml; charset=utf-8Content-Length: 2972SOAPAction: ""<?xml
version='1.0'
> encoding='UTF-8'?><SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><ns1:deploy
> xmlns:ns1="urn:xml-soap-service-management-service"
>
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><descript
> or xmlns:ns2="http://xml.apache.org/xml-soap"
> xsi:type="ns2:DeploymentDescriptor"><faultListener
> xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:Array"
> ns3:arrayType="xsd:string[1]"><item
>
xsi:type="xsd:string">org.apache.soap.server.DOMFaultListener</item></faultL
> istener><providerClass
>
xsi:type="xsd:string">samples.addressbook.AddressBook</providerClass><servic
> eType xsi:type="xsd:int">0</serviceType><serviceClass
xsi:type="xsd:string"
> xsi:null="true"/><methods
> xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:Array"
> ns4:arrayType="xsd:string[4]"><item
> xsi:type="xsd:string">getAddressFromName</item><item
> xsi:type="xsd:string">addEntry</item><item
> xsi:type="xsd:string">getAllListings</item><item
> xsi:type="xsd:string">putListings</item></methods><providerType
> xsi:type="xsd:byte">0</providerType><scriptLanguage xsi:type="xsd:string"
> xsi:null="true"/><mappings
> xmlns:ns5="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:Array"
> ns5:arrayType="ns2:TypeMapping[2]"><item
> xsi:type="ns2:TypeMapping"><encodingStyle
>
xsi:type="xsd:string">http://schemas.xmlsoap.org/soap/encoding/</encodingSty
> le><elementType-ns
>
xsi:type="xsd:string">urn:xml-soap-address-demo</elementType-ns><elementType
> -lp xsi:type="xsd:string">address</elementType-lp><javaType
>
xsi:type="xsd:string">samples.addressbook.Address</javaType><xml2JavaClassNa
> me
>
xsi:type="xsd:string">org.apache.soap.encoding.soapenc.BeanSerializer</xml2J
> avaClassName><java2XMLClassName
>
xsi:type="xsd:string">org.apache.soap.encoding.soapenc.BeanSerializer</java2
> XMLClassName></ite
>
> But the 2nd and subsequent tries end as the sample I sent yesterday:
>
> ......<methods xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/"
> xsi:type="ns4:Array" ns4:arrayType="xsd:string[4]"><item xsi:type="
>
> >From the browser, I called and ran tomcat example servlets and the call
and
> response echoed on the tunnelgui looked normal to me.
>
> How would I go about attempting to deploy from within the browser? (I do
> know that I simply get 500 errors if I try to use the SOAP deploy button
on
> the admin page.)
>
> I am trying to do all of this using tomcat, but I do have JRun set up on
the
> same system (but I do not start the services).  Still, I did set up the
> browser to use the JRun ISAPI filter and I'm a little fuzzy if this would
> have any untoward effect on what I am trying to do with tomcat/SOAP.
>
> I have not had time yet to use  echoInvoke(,,)....but I may be going there
> very soon!
>
> Tim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org