[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [bpel4people] BP-47: Determining that a people activity's task has beenskipped
In the discussion at the Nov 12 TC call, I raised the question about the
behavior of getState() if it is called for an activity that is not a
peopleActivity. The B4P spec already has a general statement "Because XPath
1.0 functions do not support returning faults, an empty node set is
returned in the event of an error", which also applies here (other XPath
functions also have a "people activity name" parameter). With that, I
withdraw my concern and vote for accepting the proposal as described :-)
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:
pic14751.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
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"Luc Clement" <luc.clement@activevos.com> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"'Michael Rowley'" <michael.rowley@activevos.com>, <bpel4people@lists.oasis-open.org> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|31.10.2008 00:48 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[bpel4people] BP-47: Determining that a people activity's task has been skipped |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Assigned: http://www.osoa.org/jira/browse/BP-47
From: Michael Rowley [mailto:michael.rowley@activevos.com]
Sent:: Thursday, October 30, 2008 17:21
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] NEW ISSUE: Determining that a people activity's task
has been skipped>
TARGET: B4P
DESCRIPTION:
There does not appear to be any reliable way for a process definition to
check if a previous activity has been skipped. Section 4.8 states: "The
people activity goes to final state Obsolete if the task is skipped."
However, there is no way for a process to include a condition that checks
the state of a people activity.
PROPOSAL:
Add a new XPath extension function called getState, with the following
entry in the table of extension functions:
getState |Returns the current|In
|state of the people|people activity name
|activity, which |(xsd:string)
|will be one of: |Out
|"INACTIVE", |the current state (xsd:string)
|"RUNNING", |
|"COMPLETED", |
|"OBSOLETE", |
|"TERMINATED" |
The state transition diagram in section 4.8 should also remove the
transitions to the "closed" state. They are currently unlabeled, which
appears to mean that the transition to "closed" happens immediately,
preventing anyone from ever seeing the states 4 states that precede
"closed".
--------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
