summaryrefslogtreecommitdiffstats
path: root/java/sca/modules/implementation-notification (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Moving current trunk modules to contrib, before starting the Equinox branch ↵lresende2008-11-1916-1181/+0
| | | | | | merge git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@718812 13f79535-47bb-0310-9956-ffa450edef68
* Change trunk version so it doesn't clash with the 1.4 branch version by ↵antelder2008-11-171-9/+9
| | | | | | bumping up to 2.0-SNAPSHOT as per the recent vote for 2.0 git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@718223 13f79535-47bb-0310-9956-ffa450edef68
* Change message getHeaders() operation to return a list, remove the QoS ↵slaws2008-09-241-4/+2
| | | | | | context and change various tests to take account of this assuming that the security information is now passed in the header. This pass the security context is not consolidated into a single subject. The tests that used to pass just a principal still do. Also add a delivery mode JMS policy test. Add some ignores. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@698457 13f79535-47bb-0310-9956-ffa450edef68
* Upgrade to Axis2 1.4.1 and its transitive dependencies such as XmlSchema and ↵rfeng2008-09-191-1/+1
| | | | | | Axiom based on the patches from Ram for TUSCANY-2606 git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@696937 13f79535-47bb-0310-9956-ffa450edef68
* More work exploring the policy extension model by implementing a token based ↵slaws2008-09-151-1/+1
| | | | | | authentication schema across binding.ws and binding.jm. No authentication is actually performed here. That is left for users to provide their own policy interceptors. However tokens are passed and security Subjects/Principals are created. This exercise has highlighted some awkwardness in the process of building policy implementations. I'll post about this on the mail list. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@695374 13f79535-47bb-0310-9956-ffa450edef68
* Use basic authentication as a motivating scenario for looking at policy plug ↵slaws2008-09-051-1/+4
| | | | | | points. Generic username/password processing is added as an interceptor. Specific axis configuration is performed by new logic specific to binding.ws which is invoked if the basic auth policy is present (we need to think about this mechanism). I added a binding-ws-axis2-policy module as a replacement for policy-security-ws but haven't moved over to it yet. I also added a message header map to Message but have only been experimenting to date. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@692411 13f79535-47bb-0310-9956-ffa450edef68
* Move Tuscany from Incubator to top level.dims2008-06-1716-0/+1180
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@668359 13f79535-47bb-0310-9956-ffa450edef68