Hi Ole,
It looks much better but I think there is still a problem with the encoding of the data since my service fails when handles the data. Comparing version 2.5.1 and 3.0.1 nightly build requests there is a difference on content-length size for the same request and file attachment.
With SopaUI 2.5.1 :
POST /nnew/fy09/fhs/DataThresholdingService HTTP/1.1
Accept-Encoding: gzip,deflate
SOAPAction: "urn:Thresholding"
Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="text/xml"; boundary="----=_Part_9_1366323247.1252965592223"
MIME-Version: 1.0
User-Agent: Jakarta Commons-HttpClient/3.1
Host: weather.aero:8094
Content-Length: 687103
------=_Part_9_1366323247.1252965592223
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID:
------=_Part_9_1366323247.1252965592223
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <402060121515>
With SoapUI 3.0.1 nightly build
POST /nnew/fy09/fhs/DataThresholdingService HTTP/1.1
Accept-Encoding: gzip,deflate
SOAPAction: "urn:Thresholding"
Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="text/xml"; boundary="----=_Part_45_1981619958.1252965655025"
MIME-Version: 1.0
User-Agent: Jakarta Commons-HttpClient/3.1
Host: weather.aero:8099
Content-Length: 687157
------=_Part_45_1981619958.1252965655025
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID:
------=_Part_45_1981619958.1252965655025
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID:
Thanks,
-Marcel
