XML Attachment Content type (goofy behavior)
Greetings all,
I am experiencing a weird behavior when I attach an XML file to a Soap Response. The Soap Response, without an attachment (in this case per the XSD), will not validate. That is expected. So I attach the XML file:
(I cache the attachement to the response as well). This validates OK. However, when I setup the Soap Request and call my mockService, the XML attachment Content type changes from text/xml to
The attachment is in the response, and can be exported to a file a just fine. But the soap response does not validate OK (alt-v), but rather I receive the following:
Any insight on why the content-type changes during the soap exchange?
Thanks in advance,
~greg
I am experiencing a weird behavior when I attach an XML file to a Soap Response. The Soap Response, without an attachment (in this case per the XSD), will not validate. That is expected. So I attach the XML file:
Content type=text/xml
Part=XMLAttach
Type=MIME
(I cache the attachement to the response as well). This validates OK. However, when I setup the Soap Request and call my mockService, the XML attachment Content type changes from text/xml to
text/xml; charset=us-ascii
The attachment is in the response, and can be exported to a file a just fine. But the soap response does not validate OK (alt-v), but rather I receive the following:
Missing attachment for part [XMLAttach] with content-type [text/xml], content type is [text/xml; charset=us-ascii]
Any insight on why the content-type changes during the soap exchange?
Thanks in advance,
~greg
