Just another bump to see if you guys had any other suggestions...
--
View this message in context:
http://cxf.547215.n5.nabble.com/More-cxf-wcf-interop-questions-tp5681573p5707815.html
Sent from the cxf-user mailing list archive at Nabble.com.
I think that's right!
It looks like the _1 references the To that is in the header but is absence
in the header and signature for the CXF policy based header.
*Is the "To" supposed to be included based on this part of the policy?*
*
Here is the correct header:*
*And the CXF header:*
Tha
Hi Daniel,
Thanks for the reply. I have been following what you suggested in terms of
allowing CXF to respond based on the WS-SecurityPolicy that is provided as
part of the WSDL. After getting all the jar dependencies and properties and
certificates set up, I am able to get the SOAP request to go
I was able to get a CXF client (generated from wsdl2java) to talk to my WCF
web service using wsHttpBinding with transport layer security. My next
issue is trying to get my CXF / Java client to invoke a different WCF
service configured with wsHttpBinding but this time with
TransportWithMessageCred
Thanks for the reply. I was getting errors like this:
System.ServiceModel.ActionMismatchAddressingException: The SOAP action
specified on the message, '', does not match the HTTP SOAP Action,
'https://schemas.investorsview.com/services/trusted/IInvestorsViewServices/Authenticate'.
at System.
I have been using CXF to generate client side Java stubs from a WCF hosted
web service with basicHttpBinding with much success. I now need to get it
to work with wsHttpBinding (for added transport and message level security)
and am running into exceptions. I have seen posts as late as last year
s
