OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-policy message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE 34: Wiring from a reference with no binding to a service witha binding


Hi folks,

 

The link for this issue in the SCA Policy TC JIRA: http://www.osoa.org/jira/browse/POLICY-34

 

Regards,

Kaanu Joshi

 

PS: The word “POLICY- ”  will be discontinued in the subject line when posting the issue link to JIRA. The issue number will follow the word “ISSUE”.


From: David Booz [mailto:booz@us.ibm.com]
Sent: Saturday, October 20, 2007 1:09 AM
To: sca-policy@lists.oasis-open.org
Subject: [sca-policy] NEW ISSUE: Wiring from a reference with no binding to a service with a binding

 

TARGET: SCA Policy Framework

DESCRIPTION:

From Mike Rowley:
The algorithm in the policy spec says that it is _not_ possible to wire from a reference that does not declare a binding (i.e. uses binding.sca) to a service that declares one or more bindings. However, I think this should be possible.

It is an unreasonable requirement to say that a service with a binding can only be the target of a reference that has that same binding. The default binding (binding.sca) should be treated as the "I don't care" binding, and should work with any binding available within the domain. Or, more precisely, any binding that can satisfy the required intents.

Starting at line 778, the policy spec states:

The wiring compatibility algorithm below determines the compatibility of a wire by a pairwise choice of a binding instance and the corresponding policySets on each side of the wire.

This should be changed to the following:

If either side of a wire does not specify a binding (or explicitly specifies binding.sca) the wire is considered to be valid for the purposes of policy processing. If both sides of the wire use binding.sca then the policies will be determined by the union of the required intents of both sides (policy sets aren't used with binding.sca). Otherwise, the bindings and policies used for the wire will be determined by adding the intents that are required by the binding.sca end of the wire to the other end of the wire and then following the 1.4.10 algorithm.

If neither side of the wire uses binding.sca, then the wiring compatibilty algorithm below is used for determining compatibility. Note that there may be many binding instances present at each side of the wire. This algorithm determines the compatibility of a wire by a pairwise choice of a binding instance and the corresponding policySets on each side of the wire.

PROPOSAL:

This should be changed to the following:

If either side of a wire does not specify a binding (or explicitly specifies binding.sca) the wire is considered to be valid for the purposes of policy processing. If both sides of the wire use binding.sca then the policies will be determined by the union of the required intents of both sides (policy sets aren't used with binding.sca). Otherwise, the bindings and policies used for the wire will be determined by adding the intents that are required by the binding.sca end of the wire to the other end of the wire and then following the 1.4.10 algorithm.

If neither side of the wire uses binding.sca, then the wiring compatibilty algorithm below is used for determining compatibility. Note that there may be many binding instances present at each side of the wire. This algorithm determines the compatibility of a wire by a pairwise choice of a binding instance and the corresponding policySets on each side of the wire.


PROVENANCE: SCA-255

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]