summaryrefslogtreecommitdiffstats
path: root/java/sca/modules/assembly-xsd/src
diff options
context:
space:
mode:
authorslaws <slaws@13f79535-47bb-0310-9956-ffa450edef68>2008-09-15 08:07:58 +0000
committerslaws <slaws@13f79535-47bb-0310-9956-ffa450edef68>2008-09-15 08:07:58 +0000
commitfa51018b6c24f598ae8174afa183b0b46436e69b (patch)
treeb6c37b85d26f0755ba95200227ea942bd2135c00 /java/sca/modules/assembly-xsd/src
parent5c5b60f1525a5865a3c2bc35263224c2cd79c713 (diff)
More work exploring the policy extension model by implementing a token based 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
Diffstat (limited to 'java/sca/modules/assembly-xsd/src')
-rw-r--r--java/sca/modules/assembly-xsd/src/main/resources/sca-binding-jms.xsd2
1 files changed, 1 insertions, 1 deletions
diff --git a/java/sca/modules/assembly-xsd/src/main/resources/sca-binding-jms.xsd b/java/sca/modules/assembly-xsd/src/main/resources/sca-binding-jms.xsd
index 6f64453635..5691bca8d1 100644
--- a/java/sca/modules/assembly-xsd/src/main/resources/sca-binding-jms.xsd
+++ b/java/sca/modules/assembly-xsd/src/main/resources/sca-binding-jms.xsd
@@ -41,7 +41,7 @@
<attribute name="requestConnection" type="QName"/>
<attribute name="responseConnection" type="QName"/>
<attribute name="operationProperties" type="QName"/>
- <anyAttribute/>
+ <anyAttribute namespace="##any" processContents="lax"/>
</extension>
</complexContent>
</complexType>