sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-assembly] NEW ISSUE: (v1.1) Remove RFC2119 language forunderspecified normative statements
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: OASIS Assembly <sca-assembly@lists.oasis-open.org>
- Date: Tue, 15 Mar 2011 09:03:51 +0000
Logged as: http://www.osoa.org/jira/browse/ASSEMBLY-260
Yours, Mike
|
|
Dr Mike Edwards
| Mail Point 137, Hursley
Park
|
|
STSM
| Winchester, Hants SO21
2JN
|
SCA & Services
Standards
| United Kingdom
|
Co-Chair OASIS SCA
Assembly TC
|
|
|
IBM Software Group
|
|
|
Phone:
| +44-1962 818014
|
|
|
Mobile:
| +44-7802-467431 (274097)
|
|
|
e-mail:
| mike_edwards@uk.ibm.com
|
|
|
|
|
From:
| Martin Chapman <MARTIN.CHAPMAN@ORACLE.COM>
|
To:
| OASIS Assembly <sca-assembly@lists.oasis-open.org>
|
Date:
| 14/03/2011 15:28
|
Subject:
| [sca-assembly] NEW ISSUE: (v1.1)
Remove RFC2119 language for underspecified normative statements |
Target: SCA Assembly v1.1 Specification
Description: A review of the optional and untested normative statements
highlights that there are a number of statements for which RFC2119 language
is inappropriate as the statement is too broad or ill defined to
be testable. Thus they do nothing to enhance interoperability and/or portability.
In these places, RFC2119 keywords need to be replaced so that the text
and sentiment is not lost but it is no longer normative. The statements
affected are: ASM12008, ASM12013, ASM12014, ASM12015, ASM12016, ASM12018,
ASM12020, ASM14001, ASM14002
Proposal:
ASM12008:
Change: "[ASM12008] An SCA runtime MAY provide the contribution operation
functions (install Contribution, update Contribution, add Deployment Composite,
update Deployment Composite, remove Contribution)."
To: "It is strongly encouraged that an SCA runtime provides the contribution
operation functions (install Contribution, update Contribution, add Deployment
Composite, update Deployment Composite, remove Contribution); how these
are provided is implementation specific."
ASM12013:
Change: "[ASM12013] For components at the Domain level, with references
for which @autowire="true" applies, the behaviour of the SCA
runtime for a given Domain MUST take ONE of the 3 following forms:
1) The SCA runtime disallows deployment of any components with autowire
references. In this case, the SCA runtime MUST raise an exception at the
point where the component is deployed.
2) The SCA runtime evaluates the target(s) for the reference at the time
that the component is deployed and does not update those targets when later
deployment actions occur.
3) The SCA runtime re-evaluates the target(s) for the reference dynamically
as later deployment actions occur resulting in updated reference targets
which match the new Domain configuration. How the reconfiguration of the
reference takes place is described by the relevant client and implementation
specifications."
To: "For components at the Domain level, with references for which
@autowire="true" applies, the behaviour of the SCA runtime for
a given Domain is implementation specific although it is expected that
ONE of the 3 behaviours below is followed:
1) The SCA runtime disallows deployment of any components with autowire
references. In this case, the SCA runtime can raise an exception at the
point where the component is deployed.
2) The SCA runtime evaluates the target(s) for the reference at the time
that the component is deployed and does not update those targets when later
deployment actions occur.
3) The SCA runtime re-evaluates the target(s) for the reference dynamically
as later deployment actions occur resulting in updated reference targets
which match the new Domain configuration. How the reconfiguration of the
reference takes place is described by the relevant client and implementation
specifications."
ASM12014:
Change: "[ASM12014] Where <wire/> elements are added, removed
or replaced by deployment actions, the components whose references are
affected by those deployment actions MAY have their references updated
by the SCA runtime dynamically without the need to stop and start those
components."
To: "Where <wire/> elements are added, removed or replaced by
deployment actions, the components whose references are affected by those
deployment actions can have their references updated by the SCA runtime
dynamically without the need to stop and start those components. How this
is achieved is implementation specific."
ASM12015:
Change: "[ASM12015] Where components are updated by deployment actions
(their configuration is changed in some way, which includes changing the
wires of component references), the new configuration MUST apply to all
new instances of those components once the update is complete."
To: "Where components are updated by deployment actions (their configuration
is changed in some way, which includes changing the wires of component
references), the SCA implementation needs to ensure that the updates apply
to all new instances of those components once the update is complete."
ASM12016:
Change: "[ASM12016] An SCA runtime MAY choose to maintain existing
instances with the old configuration of components updated by deployment
actions, but an SCA runtime MAY choose to stop and discard existing instances
of those components."
To: "An SCA runtime can choose to maintain existing instances with
the old configuration of components updated by deployment actions, although
an implementation of an SCA runtime can choose to stop and discard existing
instances of those components."
ASM12018:
Change: "[ASM12018] Where a component that is the target of a wire
is updated, future invocations of that reference SHOULD use the updated
component."
To: "Where a component that is the target of a wire is updated, an
SCA runtime can direct future invocations of that reference to the updated
component."
ASM12020:
Change: " [ASM12020] Where a component is added to the Domain that
is a potential target for a domain level component reference where that
reference is marked as @autowire=true, the SCA runtime MUST:
. either update the references for the source
component once the new component is running.
. or alternatively, defer the updating of the
references of the source component until the source component is stopped
and restarted."
To: "Where a component is added to the Domain that is a potential
target for a domain level component reference where that reference is marked
as @autowire=true, the SCA runtime can:
. either update the references for the source
component once the new component is running.
. or alternatively, defer the updating of the
references of the source component until the source component is stopped
and restarted."
ASM14001:
Change: "[ASM14001] An SCA runtime SHOULD detect errors at deployment
time where those errors can be found through static analysis."
To: " An SCA runtime is expected to detect errors at deployment time
where those errors can be found through static analysis."
ASM14002:
Change: "[ASM14002] The SCA runtime SHOULD prevent deployment of contributions
that are in error, and raise the error to the process performing the deployment
(e.g. write a message to an interactive console or write a message to a
log file)."
To: "An SCA runtime has to prevent deployment of contributions that
are in error, and raise an error to the process performing the deployment
(e.g. write a message to an interactive console or write a message to a
log file). The exact timing of checking contributions for errors
is implementation specific."
---------------------------------------------------------------------
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
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]