Problem with adding documents/attachments
I tried to add different attachments, e.g. simple txt files, pdf files, word documents etc., but I am not able to get a valid soap response (=the document is not added as expected). And the functional...
Forum Discussion
I've seen something called MTOM, and I can see we do not have it enabled on our services. However according to your documention at http://www.soapui.org/userguide/attachments.html it's supported to do it "our" way:
[glow=ligthgreen,2,300]Inline files
soapUI also has the option of "inlining" binary files into request messages when they are sent; if a message contains base64Binary or hexBinary data elements, these can be "filled" using an attached file in 2 ways:
1. By specifying a value of cid:somename and associating an attached file with the "somename" part in the same way as in the swaRef/MTOM examples above
2. By specifying the value file:filepath where file path points to a local file
In both cases, the associated file will be inlined into the message with either base64 or hex encoding. For example if the request operations' schema defines the following:
and the corresponding message would contain for example:
file:c:\data\mydata.zip
The c:\data\mydata.zip file would be inlined into the outgoing message using hex encoding.[/glow]
I've tried doing as described, but i cannot get it to work, i get the usual 415 error
[glow=ligthgreen,2,300]Inline files
soapUI also has the option of "inlining" binary files into request messages when they are sent; if a message contains base64Binary or hexBinary data elements, these can be "filled" using an attached file in 2 ways:
1. By specifying a value of cid:somename and associating an attached file with the "somename" part in the same way as in the swaRef/MTOM examples above
2. By specifying the value file:filepath where file path points to a local file
In both cases, the associated file will be inlined into the message with either base64 or hex encoding. For example if the request operations' schema defines the following:
and the corresponding message would contain for example:
The c:\data\mydata.zip file would be inlined into the outgoing message using hex encoding.[/glow]
I've tried doing as described, but i cannot get it to work, i get the usual 415 error