[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: Operation level policy attachment is broken
TARGET: SCA Policy Framework
DESCRIPTION:
The section on operation attachment is misleading, confusing and contradictory. Rather than point out all the problems, this issue proposes to start over considering the following:
- How are wires resolved if a method level intent requires a different policySet than the binding?
- What happens if policySet attachment is in use, and the operation level attachment is different from the binding, reference or service attachment?
- How are operation level intents mapped to PolicySets?
- What happens at runtime in these cases?
The following are 4 examples to consider when answering the above questions.
Assume the following policySets exist:
exa:EnterpriseIntegrityOnly - provides="sca:integrity"
exa:EnterpriseConfidentialityOnly - provides="sca:confidentiality"
(1)
<reference>
<binding.ws requires="sca:integrity">
<operation name = "method1" requires = "sca:confidentiality"/>
</binding.ws>
</reference>
(2)
<reference>
<binding.ws policySets="exa:EnterpriseIntegrityOnly">
<operation name = "method1" requires = "sca:confidentiality"/>
</binding.ws>
</reference>
(3)
<reference>
<binding.ws requires="sca:integrity">
<operation name = "method1" policySets="exa:EnterpriseConfidentialityOnly"/>*
</binding.ws>
</reference>
(4)
<reference>
<binding.ws policySets="exa:EnterpriseIntegrityOnly">
<operation name = "method1" policySets="exa:EnterpriseConfidentialityOnly"/>*
</binding.ws>
</reference>
PROPOSAL: none
PROVENANCE: SCA-223
Dave Booz
STSM, SCA and WebSphere Architecture
Co-Chair OASIS SCA-Policy TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com
http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]