Great, soapversion now ok :-)
But now getting a problem that we also had when using SaajBinding, in that
the xml response is very large as was being truncated. We fixed this locally
by extending the SaajBinding and overridng the
onMessageExchange
in particular just after the call() we added response.saveChanges(); e.g.
SOAPMessage response = connection.call(inMessage, soapEndpoint);
response.saveChanges();
I'm guessing a similar fix is required for the HttpEndPoint ?
Please would you help fix this.
--
View this message in context:
http://www.nabble.com/SAAJMarshaller---soapfault-content-getting-removed-tf1830872.html#a5061379
Sent from the ServiceMix - User forum at Nabble.com.
