There is one thing you could try, looking at the difference between the two messages. Assuming that you are using WSS4JOutInterceptor, set the "isBSPCompliant" property to "false" on the client. This will remove the " <ec:InclusiveNamespaces xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"; PrefixList="cwsh soap wsse wsu"/>" stuff from the Signature, that the original message doesn't have.
Colm. On Wed, Jan 23, 2013 at 5:15 AM, Bob Ross <supaphr...@yahoo.com> wrote: > *sigh* > I was sure this was going to work.... > > The XML request looks good to me: > Link: http://pastebin.com/DCCEts9q > > Not sure why I am still getting "Access Denied, Invalid Message" back from > their server. :( > > Is it possible the order of the elements in the SOAP Header matter? How > could I move the custom element before the wsse:Security element? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Best-CXF-client-approach-for-remote-WSDL-using-wsp-Policy-tp5721874p5722040.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
