RE: [wsbpel] New Issue - Link Semantics in Event Handlers

["Chunbo Huang" <chunbo@bea.com>]

Hi Yuzo,

I think the link status is maintained at process instance level, not based
on the thread level.  So A and B will be synced as far as they belong to the
same process instance.

-Chunbo


> -----Original Message-----
> From: Yuzo Fujishima [mailto:fujishima@bc.jp.nec.com]
> Sent: Wednesday, July 02, 2003 10:16 PM
> To: wsbpel@lists.oasis-open.org
> Subject: Re: [wsbpel] New Issue - Link Semantics in Event Handlers
>
>
> Edwin,
>
> Here goes a sample fragment:
>
> <eventHandlers>
>   <onMessage ...>
>     <flow>
>       <links>
>         <link name="AtoB"/>
>       </links>
>       <invoke name="A" ...>
>         <source linkName="AtoB"/>
>       </invoke>
>       <invoke name="B" ...>
>         <target linkName="AtoB"/>
>       </invoke>
>     </flow>
>   </onMessage>
> </eventHandlers>
>
> > > Short Description:
> > > According to 13.5.4.2 Message Events, BPEL 1.1 allows one
> > > event handler activity to run concurrently. However, it is
> > > not specified whether all concurrent "threads" share link
> > > status or each thread maintains its own link status. Suppose
> > > activity B has synchronization dependency on A. Can B in a
> > > thread be run after A is completed in other thread? Or only
> > > after A is completed in the same thread?
>
>
> ----- Original Message -----
> From: "Edwin Khodabakchian" <edwink@collaxa.com>
> To: "'Yuzo Fujishima'" <fujishima@bc.jp.nec.com>;
> <wsbpel@lists.oasis-open.org>
> Sent: Wednesday, July 02, 2003 12:03 PM
> Subject: RE: [wsbpel] New Issue - Link Semantics in Event Handlers
>
>
> > Yuzo,
> >
> > Could you please provide a BPEL code fragment that would highlight this
> > problem?
> >
> > Edwin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsbpel-help@lists.oasis-open.org
>
>