[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ISSUE 21: alwaysProvides in binding specs - Proposal
http://www.osoa.org/jira/browse/POLICY-21
Description from the JIRA:
When the specification of a binding type indicates that an intent is always
provided, does that intent have to be listed in the alwaysprovides element of a
binding.type? What happens if it is not listed, as according to the spec it is
always provided.
Proposal: Close No Action
http://www.oasis-open.org/apps/org/workgroup/sca-policy/download.php/29457/sca-policy-1%5B1%5D.1-spec-wd-07.pdf
SCA Policy FW spec WD07 - Section 4.7 explains @alwaysProvides, see lines 990-991. Combine that with section 4.10 lines 1203-1207.
The answer to the question above is that the SCA Policy FW will try to satisfy such an intent through application of a PolicySet, which would be unnecessary and possibly also produce unexpected results. I believe this is the proper behavior and therefore suggest a CNA closing of this Issue.
Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]