summaryrefslogtreecommitdiffstats
path: root/branches/sca-java-2.0-M3/itest/implementation-spring/src/main/resources/implementation/policies/definitions.xml (unfollow)
Commit message (Collapse)AuthorFilesLines
2009-06-16Create 2.0 M3 release branchantelder1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@785089 13f79535-47bb-0310-9956-ffa450edef68
2009-04-21Fixes for Spring iTestramkumar1-2/+2
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@767105 13f79535-47bb-0310-9956-ffa450edef68
2009-04-20Porting Spring iTests into 2.xramkumar1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@766686 13f79535-47bb-0310-9956-ffa450edef68
2008-12-02Branch for 1.4ramkumar1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@722428 13f79535-47bb-0310-9956-ffa450edef68
2008-11-13Creating Java SCA 1.x branchlresende1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@713805 13f79535-47bb-0310-9956-ffa450edef68
2008-10-16TUSCANY-2600: Apply patches from Ramkumar Ramalingam to Provide ITEST for ↵antelder1-29/+39
the recent Spring Implementation changes git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@705178 13f79535-47bb-0310-9956-ffa450edef68
2008-09-15More work exploring the policy extension model by implementing a token based ↵slaws1-0/+4
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