[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [bpel4people] BP-2 - RE: [bpel4people] NEW ISSUE: Title: Defer Activation Time is missing from HT protocol message
Per today’s decision, I re-opened BP-2 - http://www.osoa.org/jira/browse/BP-2
Luc Clément Active Endpoints, Inc +1.978.793.2162 | luc.clement@activevos.com From: Luc Clement
[mailto:luc.clement@activevos.com] During the review of the updates provided by Dieter relating to
incorporating deferActivation, we uncovered an issue with the
definition of deferActivation while reviewing ws-ht. The use of the
DeferActivationTime is currently specified as xsd:dateTime but the b4p spec
defines b4p:for and b4p:until elements to specify a duration and a point in
time respectively. The ws-ht spec does not account for this. Excerpt from b4p: <b4p:deferActivation>? ( <b4p:for expressionLanguage="anyURI"?>
duration-expression
</b4p:for> | <b4p:until expressionLanguage="anyURI"?>
deadline-expression
</b4p:until> ) </b4p:deferActivation> <b4p:expiration>? ( <b4p:for expressionLanguage="anyURI"?>
duration-expression
</b4p:for> | <b4p:until expressionLanguage="anyURI"?>
deadline-expression
</b4p:until> ) </b4p:expiration> We need to fix HT to correct this discrepancy. A proposal is
going to be required for this. Dave: please include this as an agenda item for the next TC
meeting. Luc Clément Active Endpoints, Inc +1.978.793.2162 | luc.clement@activevos.com From: Luc Clement
[mailto:luc.clement@activevos.com] Assigned: http://www.osoa.org/jira/browse/BP-2
From: Luc Clement
[mailto:luc.clement@activevos.com] Submitted on behalf of Mark Ford, Active Endpoints From: Mark Ford
[mailto:mark.ford@activevos.com] TARGET:
WS-HT DESCRIPTION:
There is no mechanism for passing the defer activation time to a
remote task. This value should be part of the humanTaskContext that is defined
in Section 7.4.1 of the HT specification. It is important to include this value
since the task needs to be able to enter the task management system in a
CREATED state such that an admin could select the task and activate it prior to
the defer activation time. PROPOSAL:
Update the humanTaskContext to include the defer activation value. This
involves the following change to ws-humantask-protocol.xsd: Existing
definition -
<xsd:complexType name="tHumanTaskContext"> Proposed
definition -
<xsd:complexType name="tHumanTaskContext"> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]