+1!
From: Danny van der Rijn
[mailto:dannyv@tibco.com]
Sent: Thursday, October 22, 2009 1:27 PM
To: Dieter Koenig1
Cc: sca-bpel@lists.oasis-open.org
Subject: Re: [sca-bpel] Operations on SCA Contributions Containing BPEL
Component Implementations
Yes, the SCA-BPEL spec should remain silent about these
scenarios. SCA should say as little as possible about changes to the
runtime. While it was necessary to resolve Assembly 138 this way in order
to talk about when an SCA error SHOULD or MUST be enforced, that's where it
should stop.
Dieter Koenig1 wrote:
The SCA-Assembly
spec chapter 10 describes operations on SCA contributions
(10.4) and aspects of dynamic behavior (10.7, 10.8.). Moreover, the
SCA-Assembly issue 138 resolution (almost identical to the mail below)
introduces states of an SCA artifact and state transitions caused by SCA
operations.
Should the SCA-BPEL spec remain silent about these scenarios?
IMO it does make sense to describe whether and how long(!!!)-running BPEL
process instances are affected by actions like
-- Removing a contribution
-- Adding, removing, replacing wires
-- Changing the targets of a wire
-- Changing component property values
For example,
-- a contribution containing a BPEL process implementation must not be
removed as long as there are running process instances.).
-- it could be very helpful being able to replace a wire target for a
process instance that runs for many months, e.g. if the original wire
target became obsolete
Depending on the TC's reaction I would then open an issue ...
Kind Regards
Dieter König
Senior Technical Staff Member, WebSphere Process Server Architect
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions
Phone:
+49-7031-16-3426
IBM
Deutschland
(Embedded
image moved
to file:
pic01147.gif)
E-Mail: dieterkoenig@de.ibm.com
Schönaicher Str.
220
71032
Böblingen
Germany
IBM
Deutschland
Research &
Development
GmbH
/
Vorsitzender
des
Aufsichtsrats:
Martin
Jetter
Geschäftsführung:
Erich
Baier
Sitz
der
Gesellschaft:
Böblingen
/
Registergericht:
Amtsgericht
Stuttgart,
HRB
243294
----- Forwarded by Dieter Koenig1/Germany/IBM on 20.10.2009 17:38 -----.
From: Mike Edwards <mike_edwards@uk.ibm.com>
To: "OASIS
Assembly" <sca-assembly@lists.oasis-open.org>
Date: 20.10.2009
16:20
Subject: [sca-assembly] [ISSUE 138] Assembly
specification unclear on Contribution vs Deployment - when can errors
in
artifacts be reported? - Updated Proposal
2
Here is a proposal based on discussions that have taken place on the email
list and in prevoous TC calls:
Proposal:
Add a new section to the spec after line 3649 as follows:
11.3. States of Artifacts in the Domain
Artifacts in the SCA domain are in one of 3 states:
1. Installed
2. Deployed
3. Running
Installed artifacts are artifacts that are part of a Contribution that is
installed into the Domain.
Installed artifacts are available for use by other artifacts that are
deployed, See "install Contribution"
and "remove Contribution" to understand how artifacts are installed
and
uninstalled.
Deployed artifacts are artifacts that the SCA runtime is given to execute.
Artifacts are deployed
either through explicit deployment actions or through deployment actions
that act through
<deployable/> elements present in a sca-contribution.xml file within a
Contribution. If an artifact is deployed
which has dependencies on other artifacts, then those dependent artifacts
are also deployed.
When the SCA runtime has one or more deployed artifacts, the runtime
attempts to put those artifacts
and any artifacts they depend on into the Running state. This can fail due
to errors in one or more of the artifacts
or the process can be delayed until all dependencies are available.
11.3.1
Checking for errors in artifacts MAY be done for artifacts when they are
Installed (ie where the artifacts are
simply part of installed contributions] [ASM120xx]
Errors in artifacts SHOULD be detected during the Deployment of the
artifacts. [ASM120xx]
Errors in artifacts MUST be detected no later than the process of putting
the
artifacts into the Running state, [ASM120xx]
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
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