Which service/port combination are you using from that wsdl? Each of the three have very different policies in place.
Dan On Mon April 6 2009 12:36:47 pm Ian Homer wrote: > Hi, > > Another quicky relating to our integration work between a CXF client > to WCF as described in tutorial "WCF Getting Started Sample Tutorial > with Message Security User Name" @ > http://msdn.microsoft.com/en-us/library/ms752233.aspx and as reported in a > JIRA ticket (for another issue) @ > https://issues.apache.org/jira/browse/CXF-2158 . > > The CXF client seemed to expect the body to be signed in the response > from WCF and was throwing the following exception > > INFO : Interceptor has thrown exception, unwinding now > org.apache.cxf.interceptor.Fault: These policy alternatives can not be > satisfied: > > {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SignedParts: > {http://www.w3.org/2003/05/soap-envelope}Body not signed > at > org > .apache > .cxf > .ws > .policy > .AbstractPolicyInterceptor > .handleMessage(AbstractPolicyInterceptor.java:47) > at > org > .apache > .cxf > .phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java: > 641) > at > org.apache.cxf.transport.http.HTTPConduit > $WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2108) > > > we resolved this by adding the following interceptor (as described in > https://issues.apache.org/jira/browse/CXF-215) > > bus.getInInterceptors().add(new > PolicyFilterOutInterceptor(WCF_SSLA)); > > I was wondering however whether it was the CXF client or the WCF > service that was misbehaving. Is there a policy defined that is > mandating the Body to be signed in the response from the service? > > Many thanks, > > Ian -- Daniel Kulp [email protected] http://www.dankulp.com/blog
