Hi,

I had trouble with the same problem. If you change your binding in
seismic-scencr.wsdl from soap to soap12, everything is fine.

Why did this change from 2.2.8 to 2.3.1?

Regards
Karl



>> John, you might try downloading the sample code from the 
>> SymmetricBinding article referenced by Glen
>> (http://www.ibm.com/developerworks/java/library/j-jws17/index.html)
as 
>> a basis for trying your policy. First build and test the supplied 
>> sample using your CXF installation, then substitute your policy for 
>> the one in the sample code WSDL. Hopefully that could help you find 
>> the cause of the problems.
>>


> WARNING: Interceptor for {
http://docs.oasis-open.org/ws-sx/ws-trust/200512/wsdl}SecurityTokenServi
ce#{http://docs.oasis-open.org/ws-sx/ws-trust/200512/wsdl}RequestSecurit
yToken has
> thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: Action
http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/SCT not supported
at
>
org.apache.cxf.ws.addressing.MAPAggregator.mediate(MAPAggregator.java:57
2)

Reply via email to