Can't send attachments using soapUI 3.6 Pro
Using soapUI 3.5.1, an image attached to the request I'm sending in to my system was encoded into a long string, visible in the RAW output of the request, as such:
Using soapUI 3.5 this is showing as this:
And doesn't send the attachment.
If in 3.6 I enter the string shown in the request for 3.5.1, the mock-email is successful and the image is shown. The request also contains a "part 2", which is not added to the standard 3.6 request.
Is this a bug introduced by the recent changes to attachment caching?
Apologies for the non-technical nature of this bug, I'm not a coder in any way, just using soapUI to emulate email production.
Thanks
Nik
POST http://qa01:8080/smartagent/ExternalSource HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: ""
User-Agent: Jakarta Commons-HttpClient/3.1
Host: qa01:8080
Content-Length: 1034
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdl="http://www.thisisnumero.com/xml/smartagent/4.0/wsdl" xmlns:smf="http://www.thisisnumero.com/xml/smartagent/4.0/smf">
<soapenv:Header/>
<soapenv:Body>
<wsdl:injectEmailWorkItem>
<wsdl:WorkItem>
<smf:id>Sunglasses70022</smf:id>
<smf:to>Sunglasses@localhost.com</smf:to>
<smf:from>Sunglasses7002@localhost.com</smf:from>
<smf:subject>I've a Sunglasses 7002 problem</smf:subject>
<smf:body>I've a Sunglasses 7002 problem and would like your help please</smf:body>
<smf:attachment name="tiny.jpg" contentType="image/jpeg">
<smf:value>iVBORw0KGgoAAAANSUhEUgAAAAIAAAACCAIAAAD91JpzAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAATSURBVBhXY2BgYPj//z8YMzAAACnkBftXLqYoAAAAAElFTkSuQmCC</smf:value>
</smf:attachment>
</wsdl:WorkItem>
</wsdl:injectEmailWorkItem>
</soapenv:Body>
</soapenv:Envelope>
Using soapUI 3.5 this is showing as this:
POST http://qa01:8080/smartagent/ExternalSource HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: ""
User-Agent: Jakarta Commons-HttpClient/3.1
Host: qa01:8080
Content-Length: 843
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdl="http://www.thisisnumero.com/xml/smartagent/4.0/wsdl" xmlns:smf="http://www.thisisnumero.com/xml/smartagent/4.0/smf">
<soapenv:Header/>
<soapenv:Body>
<wsdl:injectEmailWorkItem>
<wsdl:WorkItem>
<smf:id>Navy70002</smf:id>
<smf:to>Navy@localhost.com</smf:to>
<smf:from>Navy7000@localhost.com</smf:from>
<smf:subject>I've a Navy 7000 problem</smf:subject>
<smf:body>I've a Navy 7000 problem and would like your help please</smf:body>
<smf:attachment name="tiny.jpg" contentType="image/jpeg">
<smf:value>cid:jpg</smf:value>
</smf:attachment>
</wsdl:WorkItem>
</wsdl:injectEmailWorkItem>
</soapenv:Body>
</soapenv:Envelope>
And doesn't send the attachment.
If in 3.6 I enter the string shown in the request for 3.5.1, the mock-email is successful and the image is shown. The request also contains a "part 2", which is not added to the standard 3.6 request.
Is this a bug introduced by the recent changes to attachment caching?
Apologies for the non-technical nature of this bug, I'm not a coder in any way, just using soapUI to emulate email production.
Thanks
Nik
