apache-tuscany - apache tuscany

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merging the 1.x delta on top of the equinox based modules	lresende	2008-11-19	23	-0/+1906
\| \| \| \|	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@718858 13f79535-47bb-0310-9956-ffa450edef68
*	Moving current trunk modules to contrib, before starting the Equinox branch ↵	lresende	2008-11-19	23	-1906/+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 ↵	antelder	2008-11-17	1	-6/+6
\| \| \| \| \| \|	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
*	Add a reference side example of the Request Response Binding in JMS	slaws	2008-11-03	4	-0/+319
\| \| \| \|	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@710080 13f79535-47bb-0310-9956-ffa450edef68
*	Change message getHeaders() operation to return a list, remove the QoS ↵	slaws	2008-09-24	5	-15/+42
\| \| \| \| \| \|	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
*	Add in policies to support JMS message header setting. Also add in ↵	slaws	2008-09-16	11	-57/+497
\| \| \| \| \| \|	reliability intents. No policies or implementation changes to support these reliability intents here. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@695928 13f79535-47bb-0310-9956-ffa450edef68
*	More work exploring the policy extension model by implementing a token based ↵	slaws	2008-09-15	15	-0/+1120
	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