Re: [wsbpel] Issue - 107 - Proposal for Vote

[Alex Yiu <alex.yiu@oracle.com>]

Hi all,


In terms of number of activities, I would tend to agree with Yaron.
That is, exactly one.

For more than one activities case, we would put <scope>, <sequence> or 
<flow> (which is ONE activity) into the <opaque> place holder.

For zero activity case, we would put <empty> (which is also ONE 
activity) into the <opaque> place holder.

I shall mention about advantages of this ONE-activity model in my next 
email message.


Thanks!


Regards,
Alex Yiu


Rossomando, Philip wrote:

>I agree with Dieter. However, would it make sense to have
>An attribute of an opaque element provide a hint as to the
>Intended activity?
>
>Phil Rossomando
> 
>Research Director, Technology & Architecture
>Unisys Corporation
>Unisys Way, B-330
>Blue Bell, PA 19424 USA
>Philip.rossomando@unisys.com
>215-986-3998
>FAX 413-0215-2043
> 
>
>-----Original Message-----
>From: Dieter Roller [mailto:ROL@de.ibm.com] 
>Sent: Thursday, May 06, 2004 1:19 AM
>To: ygoland@bea.com
>Cc: wsbpeltc
>Subject: Re: [wsbpel] Issue - 107 - Proposal for Vote
>
>
>
>
>
>Yaron,
>
>I think it is too restrictive: an opaque activity is the place holder
>for
>any number of activities (including zero activities)...
>
>Cheers,
>
>dieter
>
>
>
>
>
> 
>
>             "Yaron Y. Goland"
>
>             <ygoland@bea.com>
>
> 
>To 
>             05/06/2004 01:43          wsbpeltc
>
>             AM                        <wsbpel@lists.oasis-open.org>
>
> 
>cc 
> 
>
>             Please respond to
>Subject 
>                  ygoland              [wsbpel] Issue - 107 - Proposal
>for 
>                                       Vote
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>
>
>
>
>An activity called 'opaque' shall be introduced for the exclusive
>use of abstract processes. The opaque activity's semantics are that it
>is a place holder for a single activity. The author of an executable
>complement of an abstract process has sole discretion as to what
>activity to replace an opaque activity with.
>
>A QNAME bpel:opaque where the bpel namespace shall be the URI
>used by the bpel spec for its own namespace shall be made available for
>use as the value of any BPEL attributes in a BPEL abstract process that
>accept a QNAME. The reserved QNAME's semantics are that it is a place
>holder for some other QNAME. The author of an executable complement of
>an abstract process has sole discretion as to what QNAME to replace a
>reserved QNAME with.
>
>
>
>  
>