On consuming a webservice, I get a response in SoapUI like shown below: an XOP attachment with the requested file (MTOM, base64-encoded). In Mendix however, the stream results into an empty String or an empty FileDocument (Binary) when the response is mapped using the XML import mapping.
Should Mendix be able to handle these webservice responses with attachments? Or is there an alternative to receive these responses?
__
Edit 20 May 2017: with help of the Mendix support team, the issue is resolved. It appeared that the MTOM implementation of the publishing party was not fully according specifications. Mendix is picky about the content-type header returned, the publishing party returned at first:
content-type: multipart/related; boundary="MIMEBoundary_d332ab067c0ccd8ca3f288cda61b94c481a05e875d98194f"; start-info="text/xml"; type="text/xml"; start="<0.c332ab067c0ccd8ca3f288cda61b94c481a05e875d98194f@apache.org>"
But this is now updated to:
content-type: multipart/related; boundary="MIMEBoundary_a355e2e848c3f59a60a85f9beff04c53caa92dc315e74dc2"; start-info="text/xml"; type="application/xop+xml"; start="<0.b355e2e848c3f59a60a85f9beff04c53caa92dc315e74dc2@apache.org>"