ISSUE-110: Should intents be ignorablel?

[David Booz <booz@us.ibm.com>]

http://www.osoa.org/jira/browse/POLICY-110

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

ashok malhotra ---11/17/2009 08:35:11 AM---The last para of section 4.12 says: "If the combination of implementationType / bindingType / collec

From:	ashok malhotra <ashok.malhotra@oracle.com>
To:	oasis policy <sca-policy@lists.oasis-open.org>
Date:	11/17/2009 08:35 AM
Subject:	[sca-policy] NEW ISSUE: Should intents be ignorablel?

---

The last para of section 4.12 says:

"If the combination of implementationType / bindingType / collection of 
policySets does not satisfy all of the intents which apply to the 
element, the configuration is not valid. However, an SCA Runtime can 
allow a deployer to force deployment even in the presence of such errors 
as long as a warning is issued or some other indication is provided that 
deployment has been forced.  Details of the behavior of the deployer in 
such situations are not specified in this specification." 

This means, essentially, that intents associated with the SCDL can be ignored.

Dale Moberg raised a question about this.  See the thread starting
http://lists.oasis-open.org/archives/sca-policy/200911/msg00016.html
Dale argues that certification becomes problematic if intents can be left
unsatisfied.

I, too, have been troubled by the language quoted above.
My feeling is that intents associated directly with a SCDL MUST be satisfied.
If they are not an error should be raised.  We need not say anything
about how the error is handled.

I suggest we open the issue and have some discussion.


-- 
All the best, Ashok

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php