We are experiencing an issue with receiving a post and being able to accept the fully qualified URI from the SOAP message and accurately identifying and locating the WSDL components. We are receiving the following SOAP Fault no matter what we try - [ISS.0088.9163] Could not retrieve WSDL for service hostname.xxx.xxxxx.xxx:ws, WSD not found.
http://hostname.xxx.xxxxx.xxxhttp://hostname.xxx.xxxxx.xxx/ws/value.inboundTransactions.Status.webservices:InboundStatus
</SOAP-ENV:Fault>

We believe it to be related to an issue with not being able to parse out the fully qualified soad address uri properly -

an excerpt from the log -

[FONT=Arial][SIZE=2][FONT=Arial][B][FONT=Courier New][COLOR=red]2009-04-23 10:42:58 EDT [ISC.0039.0001D] POST [URL]http://hostname.xxx.xxxxx.xxx/ws/value.inboundTransactions.Status.webservices:InboundStatus[/URL][/color][/font][/b][/FONT][/size]
[FONT=Arial]2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← Content-Type: text/xml
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← SOAPAction:
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← Content-Length: 1443
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← User-Agent: Java1.3.1_02
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← Host: hostname.xxx.xxxxx.xxx
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← Accept: text/html, image/gif, image/jpeg, *; q=.2, /; q=.2
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← X-Forwarded-For: x.xx.xxx.xx
2009-04-23 10:42:58 EDT [ISC.0038.0002D] ← X-SSL: decrypted=true, ciphers=“TLSv1/SSLv3 AES128-SHA”
2009-04-23 10:42:58 EDT [ISC.0038.0002D] → HTTP/1.1 500 Internal Server Error
2009-04-23 10:42:58 EDT [ISC.0038.0002D] → Set-Cookie: ssnid=09898ef0301511de8803d3d74b1469d1; path=/;
2009-04-23 10:42:58 EDT [ISC.0038.0002D] → Content-Type: text/xml; charset=UTF-8
2009-04-23 10:42:58 EDT [ISC.0038.0002D] → Content-Length: 743

Our Client and our SSL Accelerator are formatting and decrypting the data properly.

Any help would be greatly appreciated.
Thanks in advance!
SOS

[/FONT][/FONT]

Mate,
not sure if you’ve already resolved this, but I was struggling as well with the implementation and even raised a SR for this.

In the end, I was able to resolve it myself…

Basically the problem is within the actual POST call. According to the latest specifications, the POST call can use the FULL URL instead of just the directive.

In my example, I was trying to use Apache Synapse + Axis 2 to connect to a webMethods server and execute some of our webServices.

All Axis requests would end up calling:
2009-08-13 18:57:02 SGT [ISC.0039.0001D] POST [url]http://localhost:5555/ws/zzSG.myProviderYZ:myProvider[/url]

whereas webMethods only supports calling the directive itself:
2009-08-13 18:57:56 SGT [ISC.0039.0001D] POST /ws/zzSG.myProviderYZ:myProvider

As for my problems, I was able to recover by forcing the request to be HTTP 1.0 compliant and to set the POST_TO_PATH correctly.
In Synapse you can do this using:
<syn:property name=“FORCE_HTTP_1.0” value=“true” scope=“axis2” />
<syn:property name=“POST_TO_PATH” value=“true” scope=“axis2” />

I hope this will help
Otherwise drop me a line …
Ste