I'm trying to implement a webservice for a Microsoft Office protocol. It identifies itself as User-Agent: SOAP Toolkit 3.0. However I can't get it to work and now I've been able to decode the acctual SSL traffic. I'm comparing what my service responds with a working service.
The only difference I can see (except for the server header and some X- headers which shouldn't matter is that JbossWS starts the soap response like this:
while Microsoft-IIS/7.0 starts it like this:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body>
I'd be supprise if it's the namespace declarations (soap, xsi and xsd vs env) that cause the problem, although may be. Apart from that the difference is that IIS emits a xml declaration and it use double quote for the namespace declaration in envelope while JbossWS use single quote.
Is it possible to configure JbossWS to output like IIS in this case?
Any experience on interoperability on this user agent with JbossWS?
I found after extensive testing that it wasn't the SOAP part that caused the problems but that the client was very sensitive to how the payload was formatted...