You can modify a local copy of your WSDL, adding the WS-SecPol
statements, and providing your runtime client references that WSDL it
should work. (The generated Service class has a hardcoded reference to
your local WSDL.)
But there's a cleaner technique though using WSS4J interceptors -- that
allows you to configure security when there are no SecPol statements in
the WSDL. The articles at #14 here can help:
http://www.jroller.com/gmazza/entry/blog_article_index
Regards,
Glen
On 02/05/2012 04:50 AM, blicket wrote:
What if I can not modify the WSDL on the server to use ws-policy? My client
is generated.
--
View this message in context:
http://cxf.547215.n5.nabble.com/x-509-security-token-tp5150380p5457606.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
