apache-tuscany - apache tuscany

	Commit message (Collapse)	Author	Files	Lines
2009-11-11	Moving 2.x tags	lresende	1	-0/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@835151 13f79535-47bb-0310-9956-ffa450edef68
2009-07-31	Rename 2.0 M3 final RC tag	antelder	1	-0/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@799570 13f79535-47bb-0310-9956-ffa450edef68
2009-07-17	Tag 2.0 M3 RC5	antelder	1	-0/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@795006 13f79535-47bb-0310-9956-ffa450edef68
2008-12-02	Branch for 1.4	ramkumar	1	-0/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@722428 13f79535-47bb-0310-9956-ffa450edef68
2008-11-13	Creating Java SCA 1.x branch	lresende	1	-0/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@713805 13f79535-47bb-0310-9956-ffa450edef68
2008-09-24	Change message getHeaders() operation to return a list, remove the QoS ↵	slaws	1	-3/+6
	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
2008-09-15	More work exploring the policy extension model by implementing a token based ↵	slaws	1	-0/+66
	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