I am having trouble making a CXF client that works with the following WSDL: http://pastebin.com/9nCh5fBT (the actual location is client-SSL protected)
I have tried multiple approaches to generating a client that fulfills the security policies it dictates, but I'm either encrypting too much or it says my signature is invalid... I am currently trying to get a "org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor" to work with no success. I thought I read somewhere on the CXF website that "*In CXF 2.2, if the cxf-rt-ws-policy and cxf-rt-ws-security modules are available on the classpath, the WS-SecurityPolicy stuff is automatically enabled*". Does that mean it can dynamically handle all WS-Security related parts to a WSDL as long as you provide it the properties to your keystore. Is that where you make a "<jaxws:client>" in Spring and just pass it "ws-security.*" properties? I want to make sure I won't waste my time with that approach. -- View this message in context: http://cxf.547215.n5.nabble.com/Best-CXF-client-approach-for-remote-WSDL-using-wsp-Policy-tp5721874.html Sent from the cxf-user mailing list archive at Nabble.com.
