Ok I've looked into it. It appears to be a bug in SOAP UI, where it is digesting only the reference to the attachment in the SOAP Body, even though it is actually sending the correctly inlined attachment. For example, from the logs:
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="id-6E1D62DCD3FA513B7A13962858310015"><edoc:uploadFormDocument xmlns:edoc="http://cmp.vba.va.gov/external/eDocumentService/";><edoc:formDocument ID="1" Veteran_Person_ID="1234567890" actionable="false" externalID="100" filename="fw4.pdf" newMail="false" veteranFirstName="Will" veteranLastName="Hard" veteranMiddleName="Work"><cmp:docContent xmlns:cmp=" http://cmp.vba.va.gov/cmp ">cid:fw4-1.pdf</cmp:docContent></edoc:formDocument></edoc:uploadFormDocument></soapenv:Body> The docContent should contain the inlined BASE-64 encoded attachment instead of the reference here. CXF can handle this correctly. I will send you a simple maven-based project that shows how to do this. Colm. On Fri, Mar 28, 2014 at 4:11 PM, chaij <[email protected]> wrote: > eDocumentServiceDDCWithSecurity-sample-soapui-project.xml > < > http://camel.465427.n5.nabble.com/file/n5749509/eDocumentServiceDDCWithSecurity-sample-soapui-project.xml > > > > Thanks for looking into it. I have attached the soapui project. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/WSS4JInInterceptor-The-signature-or-decryption-was-invalid-tp5749409p5749509.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
