[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue - 250 - How do we deal with extensionActivities thatcontain other activities that have <sources> or <targets>?
Yes, this should be addressed in an issue - I submitted a new one ("
ExtensionActivity and Start Activities", will appear soon on the list).
Kind Regards
DK
Danny van der
Rijn
<dannyv@tibco.com To
> wsbpel@lists.oasis-open.org
cc
29.03.2006 02:15
Subject
Re: [wsbpel] Issue - 250 - How do
we deal with extensionActivities
that contain other activities that
have <sources> or <targets>?
Perhaps this is a new issue; perhaps not.
The list of illegal things to have in an extension activity should be
expanded to include start activities:
IF:
- an extension activity that is not mustUnderstand=yes MUST NOT be a start
activity. It also MUST NOT contain start activities.
ws-bpel issues list editor wrote:
This issue has been added to the wsbpel issue list with a status of
"received". The status will be changed to "open" if a motion to open
the issue is proposed and that motion is approved by the TC. A motion
could also be proposed to close it without further consideration.
Otherwise it will remain as "received".
The issues list is posted as a Technical Committee document to the
OASIS WSBPEL TC pages on a regular basis. The current edition, as a
TC document, is the most recent version of the document entitled in
the "Issues" folder of the WSBPEL TC document list - the next posting
as a TC document will include this issue. The list editor's working
copy, which will normally include an issue when it is announced, is
available at this constant URL.
Issue - 250 - How do we deal with extensionActivities that contain
other activities that have <sources> or <targets>?
Status: received
Date added: 21 Mar 2006
Categories: links
Date submitted: 21 March 2006
Submitter: Danny van der Rijn
Description: The semantics of an <extensionActivity> may be such that
it may contain other activities. Those activities may contain
<sources> and/or <targets> that refer to links defined in a <flow>
that is NOT a child (at any level of nesting) of the
<extensionActivity>
10.7 states that the <extensionActivity> is treated as an empty
activity if the mustUnderstands of the extension it contains is 'no',
so removing these nested <sources> and <targets> would be illegal.
Co-submitter: Rania Khalaf
Submitters' Proposal:
Since turning the extensionActivity into an <empty> activity would
lose such sources or targets, the extensionActivity must not be
ignored. Therefore
IF:
- a link crosses the boundary of an <extensionActivity> (see precise
definition of "cross" in 11.6, Flow),
THEN:
the extension element referring to the namespace of the
<anyElementQName ..> child of the <extensionActivity> MUST have
mustUnderstand=yes.
For example, consider the case that
a flow defines a link, "l", AND
the flow contains an <extensionActivity>, whose anyElementQName
is <foo:bar>, xmlns:foo="http://example.com/foo"; AND
<foo:bar> contains another activity, "a", at any level of
nesting that EITHER:
contains a <source> that references "l" and/or
contains a <target> that references "l"
THEN: the process MUST have the element below in its extensions
section:
<extension namespace="http://example.com/foo";
mustUnderstand="yes"/>
Changes: 21 Mar 2006 - new issue
To comment on this issue (including whether it should be accepted),
please follow-up to this announcement on the
wsbpel@lists.oasis-open.org list (replying to this message should
automatically send your message to that list), or ensure the subject
line as you send it starts "Issue - 250 - [anything]" or is a reply
to such a message. If you want to formally propose a resolution to an
open issue, please start the subject line "Issue - 250 - Proposed
resolution", without any Re: or similar.
To add a new issue, see the issues procedures document (but the
address for new issue submission is the sender of this announcement).
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--------------------------------------------------------------------- To
unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. You may a link to this group and all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]