On 01/23/2013 11:55 AM, Bob Ross wrote:
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...
To rearrange elements, maybe there's something in the transformation
features you can use (
http://cxf.apache.org/docs/transformationfeature.html), maybe using SAAJ
(which is kind of clumsy but here:
http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors,
search on " AddSOAPHeaderOutInterceptor"). But I rarely hear about a
need to rearrange SOAP elements within headers, and if you tried so
there's also a risk of signatures on the header becoming invalid as a
result.
So you're not barking up the wrong tree, you might want to use Wireshark
to grab what CXF is sending, then paste it into soapUI and do your
rearranging there to test that theory to see if it makes a difference.
Although it might still fail with the rearranging even though such
rearranging is correct, due to signature failures, timestamp expiration
or other matters.
HTH,
Glen
--
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.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
