Colm,
Looks like the client is now good only need to fix some
interoperability issues
I am getting now response looks like WCF service does not like my execute
request call parameters
<IEPDResponse>Error: Value cannot be null. Parameter name:
s</IEPDResponse></ExecuteResponse></s:Body></s:Envelope>Response: Error:
Value cannot be null. Parameter name: s
No namespace errors on server now.Only one thing we are seeing is that two
additional namespaces on request do i need to get rid of those?
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
<ExecuteRequest
xmlns="http://xxxx/goodnamesapce/2008/09";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-2-4-1-Client-is-giving-the-signature-or-decryption-was-invalid-tp4507027p4522336.html
Sent from the cxf-user mailing list archive at Nabble.com.
