diff options
author | slaws <slaws@13f79535-47bb-0310-9956-ffa450edef68> | 2009-02-12 13:33:16 +0000 |
---|---|---|
committer | slaws <slaws@13f79535-47bb-0310-9956-ffa450edef68> | 2009-02-12 13:33:16 +0000 |
commit | 441f2a6396d90bccfa513f3789c26518732ea1f1 (patch) | |
tree | 2777cc39f0232727d6117b428a307a0e6361077d /branches/java-post-M1/spec | |
parent | e91b3ceec7478d30026cb2d0021fe4591455acd6 (diff) |
TUSCANY-2824 - turn WSSecurity based policy back on. Two not so great fixes here. Firstly WSSecurityPolicyHandler pushes a property into the Axis configuration context to force Rampart to recognize the policy. I haven't discovered what part of our configuration is required to do this properly. Secondly I fixed the helloworld-ws-service-secure test case to reference the wsdl on binding.ws. Without this you get a NPE in axis/rampart as it fails to map binding operations to port type operation using QNames (don't know why it thinks these are QNames). Our generated WSDL has the generated binding in a different namespace to the port type. Associating the wsdl binding with binding.ws means that the binding is not generated at the made up QNames match. I also updated a few key stores as the runtime was complaining about X509 certificate version numbers.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@743732 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'branches/java-post-M1/spec')
0 files changed, 0 insertions, 0 deletions