| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
handlers are now present but commented out as they are causing problems in the Axis 1.4.1 stack. Update the keys for the binding.ws tests cases so they remain valid for a long time.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@743002 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@722441 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@718889 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@713805 13f79535-47bb-0310-9956-ffa450edef68
|
