It's often ugly to embed Rampart and Rahas configuration information
(e.g., <ramp:RampartConfig
xmlns:ramp="http://ws.apache.org/rampart/policy"> element, along with
parameters such as "sct-issuer-config" used by Rahas) directly in WSDL
or policy documents, especially when using client code generation for
the policy handling (since the keystore information and such may change
between development and deployment). Is there a more direct way of
passing this configuration information through the Axis2 client API?
Thanks,
- Dennis
--
Dennis M. Sosnoski
Java XML and Web Services
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117