Hi,
Been comparing the full message that SoapUI generates if I call an operation against what my SAAJ java client generates. I noticed that my call doesn't have a "SOAPAction: """ in the HTTP headers. So I added that. No difference.
I then noticed that SoapUI adds a "start" element to the Content-Type header as:
Content-Type: multipart/related; type="text/xml"; start="<rootpart@soapui.org"; boundary="----=_Part_0_1576039226.1364199376012"
and that it has the Content-ID header of the SOAP Part set to that start value as well.
I tried to tweak the Content-Type header that my SAAJ client program generates, but that fails:
msg.getMimeHeaders().addHeader("Content-Type", "start=\"rootpart\"");
This generates a SAAJ exception when calling msg.saveChanges(). I do somehow think that this missing "start" element is the reason why calling a SOAP UI Mock Service from my SAAJ client program is failing. In which case: is that a bug in SoapUI?
Maarten
