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 1093 - How would the blocking guard condition semantics would be projected to BPEL?
Summary: How would the blocking guard condition semantics would be projected to BPEL?
Status: CLOSED DUPLICATE of bug 1068
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:
Depends on:
Blocks:
 
Reported: 2005-02-07 15:55 UTC by Greg Ritzinger
Modified: 2005-08-03 15:39 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2005-02-07 15:55:01 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-15 20:36:03 UTC 

*** This bug has been marked as a duplicate of 1068 ***
Comment 2 Martin Chapman 2005-05-10 16:36:15 UTC 
marked as closed because of dupl.