sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: ASSEMBLY-136: Promoting a reference with multiplicity 1..n andtargetsshould default to 0..n - Updated Proposal
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: "OASIS Assembly" <sca-assembly@lists.oasis-open.org>
- Date: Wed, 29 Jul 2009 12:39:22 +0100
Folks,
Here is a proposal for Issue 136
Concepts in the proposal:
1) A component reference can explicitly
declare as many targets as are compatible with its multiplicity
2) When a component reference is promoted,
IF the composite reference(s) is configured with at least 1
target (ie through the component that
uses the composite) then the composite reference targets OVERRIDE
the targets declared on the component
reference (ie the component reference targets are not used)
3) When a component reference is promoted,
IF the composite reference(s) has 0 targets configured
then any targets declared on the component
reference are used (ie the declared targets act as default targets)
4) For x..n component references, it
is possible to mark the reference @nonOverridable="true". In
this case,
the set of targets which are used for
the reference is the set configured on any composite references which promote
the reference PLUS the set of targets
declared on the reference itself.
5) For x..1 component references, @nonOverridable="true"
means that the reference cannot be promoted.
6) To set policy (etc) for "internal"
references:
- use intents
- or attach policySets using ExternalAttachment
- or attach policySets directly
(since they can't be configured at all
by promotion)
7) The default multiplicity of a composite
reference is determined by:
- the multiplicities of the component
references it promotes
- whether (all) the promoted component
references have at least 1 target declared
with the principle being that the multiplicity
must be set to ensure that the component references will have
their multiplicity satisfied - 0..x
is allowed for the case where the component reference is 1..x, if there
is
a target declared on (all) the component
references.
I've done the formal proposal as a marked
up version of CD03-Rev2 (all changes were accepted BEFORE
adding the changes for this proposal)
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33566/sca-assembly-1.1-spec-cd03-Rev2%2BIssue136.pdf
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33565/sca-assembly-1.1-spec-cd03-Rev2%2BIssue136.doc
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]