surffer_dude
New Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: SOAP UI MTOM attachmemt problems.
Hi, I don't know if this is really a solution for the problem, but I seem to have some sort of workaround for this by creating a new Project. Newly created project wraps only the binary element for MTOM. Maybe someone from smartbear could comment this...3.7KViews0likes0CommentsRe: SOAP UI MTOM attachmemt problems.
Hi, I have here exactly the same problem. When enabling MTOM = true also some other elements are changed into unexpected format. -- This was sent --- <mes:Attachments> <com:name>Jellyfish.jpg</com:name> <com:mimeType>image/jpeg</com:mimeType> <com:data>cid:Jellyfish.jpg</com:data> </mes:Attachments> --- This was received by the WS-Endpoint --- <mes:Attachments> <com:name><inc:Include href="cid:http://www.soapui.org/83397145883111" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></com:name> <com:mimeType><inc:Include href="cid:http://www.soapui.org/83397146167615" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></com:mimeType> <com:data><inc:Include href="cid:Jellyfish.jpg" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></com:data> </mes:Attachments> ------------------- But this gets even more strange. On my team mate's workstation this is working as expected. There only the base64binary type element ( data ) got wrapped for XOP include. We are both having the SoapUI 5.2.0 version ( latest ).3.7KViews1like1Comment