summaryrefslogtreecommitdiffstats
path: root/java/sca/modules/binding-jms-policy/pom.xml (unfollow)
Commit message (Collapse)AuthorFilesLines
2009-01-31Moving modules that are not part of the main build to contrib folderlresende1-94/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@739505 13f79535-47bb-0310-9956-ffa450edef68
2008-11-19Merging the 1.x delta on top of the equinox based moduleslresende1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@718858 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-11-03Add a reference side example of the Request Response Binding in JMSslaws1-0/+19
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@710080 13f79535-47bb-0310-9956-ffa450edef68
2008-09-16Add in policies to support JMS message header setting. Also add in ↵slaws1-0/+6
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
2008-09-15More work exploring the policy extension model by implementing a token based ↵slaws1-0/+69
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