OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: BP-35: Value and semantics of suspend/resume

Assigned: http://www.osoa.org/jira/browse/BP-35


From: Michael Rowley [mailto:michael.rowley@activevos.com]
Sent: Wednesday, September 03, 2008 17:40
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] NEW ISSUE: Value and semantics of suspend/resume






Suspend and resume are currently available to all tasks irrespective of the state they are in.  They are also available to the business owner of the task.


It is not clear what the value is of having suspend be available to the owner of a claimed or started task.  The specification implies (although it should state it explicitly) that escalations and deadlines continue as scheduled irrespective of the use of suspend.  So, why would an owner suspend his own task, especially when the owner is already able to stop and later re-start a task?


More generally, what are the semantics of suspend?  They aren’t really explained in the current spec, except in relation to the state diagram in section 4.7.




(Actually more of a suggested course of investigation)


Perhaps task suspension should be available only to roles other than the owner or potential owner role (such as business administrators) with a purpose of preventing tasks from being claimed or worked on by owners.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]