Search:

You can see from the output of the failing call that the InputStream for the response was not returning anything since it was already closed as noted by the empty brackets "[Received response [] for...

[2007:12:03:11:19:05:562] [main] [DEBUG] [org.springframework.ws.client.core.WebServiceTemplate] [logResponse] [WebServiceTemplate.java] [609] [Received response [<SOAP-ENV:Envelope...

And here is the output of the web service client call that works after patching the org.springframework.ws.transport.http.HttpUrlConnection class:


[2007:12:03:11:19:05:250] [main] [INFO]...

[2007:12:03:10:53:35:296] [main] [DEBUG] [org.springframework.ws.client.core.WebServiceTemplate] [logResponse] [WebServiceTemplate.java] [609] [Received response [] for request [<soapenv:Envelope...

[2007:12:03:10:53:34:984] [main] [INFO] [org.springframework.ws.soap.saaj.SaajSoapMessageFactory] [afterPropertiesSet] [SaajSoapMessageFactory.java] [111] [Creating SAAJ 1.2 MessageFactory]...

OK, After mucking around in the Spring-WS source (ver 1.0.2) last night, as well as reading other posts on this forum, I have determined that the differences in SAAJ implementations have not been...

Hi geo,

No, I am not currently using Websphere a for either the client or the server but eventually I will be using Websphere 6.1 to host the web service. I am using JAXB2 on Tomcat currently and...

I am running into the exact same error when running under JRE 1.4 as a spring-ws client hitting my spring-ws 1.0.2 web service running under JRE 1.5 with Tomcat 5.5.

When I use SoapUI (jre 1.5) as...