Have a document (in the format of a C4 binary image) and an XML file that contains a digital signature for the document. The digital signature contains a URI reference to the document (i.e., the C4 file). If I use SoapUI to move the C4 and XML files, SoapUI changes not only the path to the files (which is understandable) but also the filenames. The change to the filenames, particularly for the C4 document, makes it impossible to validate the digital signature in the XML file, since the URI to the C4 document is hopelessly broken. Is there a work around for this situation? Thanks.

The files come down as attachments (as part of the response) from the SOAP server.  The attachments have are given an alphanumeric string as an id. A file or document that starts life as "/export/home/frank/123.C4" on one system ends up "/newpath/.../foo.C4", and "/export/home/frank/123.XML" ends up "/newpath/.../foo.XML" after the SoapUI operation.

My problem is, the digital signature in 123.XML (foo.XML) references a URI of 123.C4 and not foo.C4. Hence digital signature validation fails, since the XMLDSIG cannot resolve the URI reference.

Thanks for your time.

Is the below what you need? Thanks for your time.

Actual file id is:T-251-530,64959,,,1,0001,0001,,
But note cid

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soap:Body>
      <ns1:getDimDataFileByFileIdentifierResponse xmlns:ns1="http://service.server.dim.jtdi.cryptek.com">
         <ns1:out ns2:mimeType="application/octet-stream" xmlns:ns2="http://www.w3.org/2004/11/xmlmime">
            <Include href="cid:119990643292810670-421333643@http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2004/08/xop/include"/>
         </ns1:out>
      </ns1:getDimDataFileByFileIdentifierResponse>
   </soap:Body>
</soap:Envelope>