I've been using Axis1.x to access my webservice using WSDL2Java generated
stubs...works great...I use the Locator class.

I've modified my webservice to use WS-Policy directives (Sign and Auth).
The WSDL has changed as expected to include the <wsp:policy> elements for
Sign and Auth.

Do I need to use Axis2/Rampart to generate the client stubs and apply the
encryption now that my webservice is using WS-Policy directives?
Is there an example for using Axis/Axis2 to access a policy-enabled web
service?

My webservice is deployed to WLS 9.2 and I can use weblogic's
clientgen-generated stubs to encrypt and digitally-sign the
message.  However, I would like my clients to be able to use Axis.
I've been trying to use Axis2/Rampart but can't get it working.
I've been getting an 'InvalidKeyException:  Wrong key usage'.

Follow on question would be with WS-Policy Auth.xml does that mean I should
use the Encrypt item in the OutflowSecurity parameter for Rampart?  Does
WS-Policy Sign.xml map to the Signature item in OutflowSecurity?  What
WS-Policy would cause me to need to use the Timestamp item in
OutflowSecurity?

Thank you in advance
Brian

Reply via email to