axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yampolsky, Robert" <ryamp...@harris.com>
Subject RE: SOAPAction or URL to locate service?
Date Fri, 01 Jul 2005 16:13:21 GMT
>However, as your local client is working, it looks to me that none of
>the above are possible.

>One other possibility is that the user account under which Apache
>process is run cannot access the directory where the server
>implementation (the .so file) is located. Give full read/write access
to
>this folder (using chmod -R 777) and try.

I think this would also apply to the local test that works.  After all
only the client is running as my non-root user.  The server is running
with Apache's privileges in both the local and remote cases.  This
applies to all the system config checks you suggested too (but I checked
them anyway).

Finally, I tried running a version of the client I built using gSoap on
both the local machine and on another machine on my network, and it
worked from both places.  Interestingly, the HTTP header produced by the
gSoap client looks a lot like the header produced by the
www.soapclient.com client (the remote client that fails), except for the
order of things and the fact that www.soapclient.com uses HTTP/1.0.

Here's what the gSOAP client produces (which works locally and
remotely):

POST /axis/HUB_TO_HUB
HTTP/1.1
Host: 172.16.48.246
User-Agent: gSOAP/2.7
Content-Type: text/xml;
charset=utf-8
Content-Length: 598
Connection: close
SOAPAction: "HUB_TO_HUB#HUB_Request"

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns1="http://www.ebizformedia.com/hub">
<SOAP-ENV:Body>
<ns1:Hub_Request>
<ns1:TO_TP>A</ns1:TO_TP>
<ns1:FROM_TP>B</ns1:FROM_TP>
<ns1:TO_HUB>C</ns1:TO_HUB>
<ns1:FROM_HUB>E</ns1:FROM_HUB>
<ns1:UID>F</ns1:UID>
<ns1:APIKEY>G</ns1:APIKEY>
<ns1:ROUTING>not supported</ns1:ROUTING>
</ns1:Hub_Request>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


And here's what www.soapclient.com produces (which doesn't work
remotely):

POST /axis/HUB_T0_HUB
HTTP/1.0
User-Agent: SQLData Client/3.02
Host: 156.43.4.68:80
Connection: Close
Accept: */*
Content-Length: 964
SOAPAction: "HUB_TO_HUB#HUB_Request"
Content-Type: text/xml;
charset="utf-8"

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://www.ebizformedia.com/hub"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema".>
<SOAP-ENV:Body>
<tns:Hub_Request.xmlns:tns="http://www.ebizformedia.com/hub">
<tns:TO_TP>AAA</tns:TO_TP>
<tns:FROM_TP>BBB</tns:FROM_TP>
<tns:TO_HUB>CCC</tns:TO_HUB>
<tns:FROM_HUB>DDD</tns:FROM_HUB>
<tns:UID></tns:UID>
<tns:APIKEY>FFF</tns:APIKEY>
<tns:ROUTING>GGG</tns:ROUTING>
<tns:MESSAGE></tns:MESSAGE>
</tns:Hub_Request>
</SOAP-ENV:Body>
</SOAPENV:Envelope>

R o b   Y a m p o l s k y
Harris Corporation, BCD
(212) 303 4250


Mime
View raw message