This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1068 - How are the blocking guard condition semantics would be projected to BPEL?
Summary: How are the blocking guard condition semantics would be projected to BPEL?
Status: CLOSED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Last Call Comment: Confirmed Closed (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: Martin Chapman
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
: 1093 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-01-31 15:28 UTC by Greg Ritzinger
Modified: 2005-09-28 22:12 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2005-01-31 15:28:05 UTC 
Not sure if this is a suitable last call topic - but just wanted to raise the
issue for discussion.

I would like to understand how the blocking guard condition semantics would be
projected to BPEL.

I also think that having the timeout functions included within the conditional
expression may make projecting to BPEL difficult - especially where the
conditional expression contains other elements: e.g.

(var1 and hasDeadlinePassed(..)) or (var2=x and hasDurationPassed(...))
Comment 1 Martin Chapman 2005-02-14 21:34:21 UTC 
From 8-feb-05 concall:
http://lists.w3.org/Archives/Member/member-ws-chor/2005Feb/att-0003/Minutes-
02082005-0.txt

ASSIGN 1068 TO THE PRIMER
Comment 2 Martin Chapman 2005-02-15 20:36:03 UTC 
*** Bug 1093 has been marked as a duplicate of this bug. ***
Comment 3 Martin Chapman 2005-05-10 16:19:56 UTC 
Gary has been informed of the group's decision [1] and we are 
awaiting 
confirmation. Category changed to LCC: Closed.

[1] http://lists.w3.org/Archives/Public/public-ws-chor-
comments/2005May/0015.html