I think I figured out why it's MIME'd. It's a migration issue from WSE
2.0 to 3.0. WSE 3.0 SoapEnvelope class now subclasses XopDocument,
Kurt Ng wrote:
> Hi,
>
> I am trying to send TCP SOAP messages with WSE 3.0, but all of the
> messages are MIME'd, which I don't want. I cannot seem to turn this
> off. I have the project MTOM settings set to the following in Visual
> Studio:
>
> Client Mode = Off
> Server Mode = never
> MaxMimeParts = 64 (default)
> Require Soap Envelope First = checked (default)
>
> Does anyone have an idea about why the messages keep coming up like
> this? Is there another way other than MTOM settings to turn off this
> MIME formatting? Thanks.
>
> Kurt
>
>
>
> example message:
>
> .
> ...-.)...<urn:uuid:002d387b-6d78-4fbc-ac12-cc560fc55b6a...
http://schemas.xmlsoap.org/soap/envelope/... >
> MIME-Version: 1.0
>
> Content-Type: multipart/related; type="application/xop+xml";
> boundary=--MIMEBoundary633202879464843750;
> start="<0.633202879464843750@example.org>"; start-info="text/xml;
> charset=utf-8"
>
>
>
>
>
> ----MIMEBoundary633202879464843750
>
> content-id: <0.633202879464843750@example.org>
>
> content-type: application/xop+xml; charset=utf-8; type="text/xml;
> charset=utf-8"
>
> content-transfer-encoding: binary
>
>
>
> <soap:Envelope xmlns:xop="
http://www.w3.org/2004/08/xop/include" > xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing" > xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><wsa:Action>get</wsa:Action><wsa:To>soap.tcp://dhcp009.foo.com/commander</wsa:To></soap:Header><soap:Body><command>get</command></soap:Body></soap:Envelope>
>
>