summaryrefslogtreecommitdiffstats
path: root/java/sca/modules/binding-jms-policy/src/test (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Change message getHeaders() operation to return a list, remove the QoS ↵slaws2008-09-241-1/+1
| | | | | | 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 ↵slaws2008-09-163-36/+130
| | | | | | 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 ↵slaws2008-09-151-0/+36
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 18:51:15 +0000