apache-tuscany - apache tuscany

	Commit message (Collapse)	Author	Age	Files	Lines
*	TUSCANY-2790 - Updated package names from org.osoa.sca to org.oasisopen.sca ↵	mcombellack	2009-01-28	3	-6/+6
\| \| \| \| \| \| \| \| \| \| \| \| \|	and from org.osoa.sca.annotations to org.oasisopen.sca.annotation to reflect the new package names in the OASIS Open SCA specifications. To do this, I: * Renamed the org.osoa.sca package to org.oasisopen.sca using Eclipse refactoring * Renamed the org.osoa.sca.annotations package to org.oasisopen.sca.annotation using Eclipse refactoring * Did a global search and replace for all remaining instances of the old org.osoa package names and replaced with the new org.oasisopen version Hopefully, I have not missed too many instances of the old package name git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@738490 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	-7/+7
\| \| \| \| \| \|	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
*	More work exploring the policy extension model by implementing a token based ↵	slaws	2008-09-15	8	-0/+483
	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