soalightning |
Newbie |
|
Phoenix, AZ (USA) |
|
|
None Specified |
|
Wednesday, November 20, 2013 |
Thursday, December 5, 2013 3:54:38 PM |
2 [0.01% of all post / 0.00 posts per day] |
|
vlad wrote:Doesn't the feature "Insert encoded External File" where you can choose base16 or base64 encoding actually do what you want?
Thanks Vlad.
However and while I can emulate base64 encoded with this technique (simple, embedding encoded content as element data in payload of a message), I have not been able get the SOAP Client or validation to correctly recognize the MTOM recommendation or SOAP with Attachments. I've read the user guide, but it doesn't speak to the requirements of those specifications (e.g. things like xop).
e.g. http://www.w3.org/TR/soap12-mtom/ http://www.w3.org/TR/xop10/
Perhaps I am missing something ?
|
Feature Request for: MTOM and also for SOAP w/Attachments (consideration for MIME, xop, base64 binary encoding)
Currently, the XML Spy Enterprise 2014 does not provide support for attachments (e.g. MTOM, SOAP w/Attachments, xop). There is support for base64 encoding, but at more of an xsi type level (schema) than with encoded attachments.
It would be a great feature if I could use the SOAP Client and submit/receive attachments (MTOM, SOAP w/Attachments)
I searched the forums and the only posts I could find were questions from 2008/2009 re: MTOM and xop. The response was not supported.
THis is 2014 and MTOM is becoming more frequently applied for SOAP/Web Services.
Thanks
|
|