billfry
11 years agoNew Contributor
MTOM odd behavior
Hi all,
I may be showing a bit of newbieness, but I'm looking for help with some unexpected/odd MTOM behavior with SoapUI 4.6.2.
When MTOM is not enabled all works as expected with my web service, though I'm not getting MTOM configured content (as expected).
When MTOM is enabled, it encodes all the content within every single XML tag, regardless of what it is. (unexpected). So it's not just encoding attachments, but rather every little content detail.
For example,
This:
-=snip=-
<nc:DocumentIdentification>
<nc:IdentificationID>251a3760-fa20-451d-b6a9-bf3b3cab6188</nc:IdentificationID>
</nc:DocumentIdentification>
-=snip=-
becomes this:
-=snip=-
<nc:DocumentIdentification>
<nc:IdentificationID>MjUxYTM3NjAtZmEyMC00NTFkLWI2YTktYmYzYjNjYWI2MTg4</nc:IdentificationID>
</nc:DocumentIdentification>
-=snip=-
with a bunch of these below it:
-=snip=-
------=_Part_252_1502108040.1387551646270
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-Id: <http://www.soapui.org/5529055332511>
251a3760-fa20-451d-b6a9-bf3b3cab6188
-=snip=-
I've looked for settings to change, or known issues, but cannot find anything to explain what's going on or how to affect it. It doesn't seem like that follows the MTOM specs, but I'm not certain about that. I just need to encode attached binary files.
Any help or guidance would be greatly appreciated.
Merry Christmas, and blessings to all!
Bill.
I may be showing a bit of newbieness, but I'm looking for help with some unexpected/odd MTOM behavior with SoapUI 4.6.2.
When MTOM is not enabled all works as expected with my web service, though I'm not getting MTOM configured content (as expected).
When MTOM is enabled, it encodes all the content within every single XML tag, regardless of what it is. (unexpected). So it's not just encoding attachments, but rather every little content detail.
For example,
This:
-=snip=-
<nc:DocumentIdentification>
<nc:IdentificationID>251a3760-fa20-451d-b6a9-bf3b3cab6188</nc:IdentificationID>
</nc:DocumentIdentification>
-=snip=-
becomes this:
-=snip=-
<nc:DocumentIdentification>
<nc:IdentificationID>MjUxYTM3NjAtZmEyMC00NTFkLWI2YTktYmYzYjNjYWI2MTg4</nc:IdentificationID>
</nc:DocumentIdentification>
-=snip=-
with a bunch of these below it:
-=snip=-
------=_Part_252_1502108040.1387551646270
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-Id: <http://www.soapui.org/5529055332511>
251a3760-fa20-451d-b6a9-bf3b3cab6188
-=snip=-
I've looked for settings to change, or known issues, but cannot find anything to explain what's going on or how to affect it. It doesn't seem like that follows the MTOM specs, but I'm not certain about that. I just need to encode attached binary files.
Any help or guidance would be greatly appreciated.
Merry Christmas, and blessings to all!
Bill.