| Commit message (Collapse) | Author | Files | Lines |
|
interesting thing that should have been obvious but which I didn't notice before. The MessageContext coming from a JAXWSProvider is a JAXWS MessageContext and we are expecting an Axis MessageContext in our existing code.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@957987 13f79535-47bb-0310-9956-ffa450edef68
|
|
debug some samples and see if there is any mileage in this approach
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@957864 13f79535-47bb-0310-9956-ffa450edef68
|
|
out existing Axis integration so I'm saving the current state and thinking about moving back to improving the integration based on our existing module.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@953602 13f79535-47bb-0310-9956-ffa450edef68
|
|
the old binding to integrate the Axis2 runtime with our servler container.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@953017 13f79535-47bb-0310-9956-ffa450edef68
|
|
ws binding so that we can exploit Axis policy and protocols. Very early days so not ready for trunk yet.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@952627 13f79535-47bb-0310-9956-ffa450edef68
|