Thanks. I did add that property and it did eliminate those extra statements. Still got the Invalid Message error. :(
I am waiting on a reply back from their IT Group, which is ungodly slow of course. While I'm waiting... Is there a way to make the custom CWSHeader element to show up first in the header? (before the binary security token data). I'm afraid they are doing something dumb like a hand written XML parser with no real web service framework on the server side at this point and the XML is going to have to match EXACTLY... -- View this message in context: http://cxf.547215.n5.nabble.com/Best-CXF-client-approach-for-remote-WSDL-using-wsp-Policy-tp5721874p5722084.html Sent from the cxf-user mailing list archive at Nabble.com.
