RE: [wsbpel] Issue - 151 - Allow a new process instance to be created by "pick onAlarm until"

["Eckenfels. Bernd" <B.Eckenfels@seeburger.de>]

Hello,

I would suggest each BPEL runtime system can define its own "TimeEvent" message/port, and you simply receive from it. Correlating to the right event can be done in two ways:

a) the engine generates a port for each of its schedulers
b) multiple process definitions can concurrently receive that initial message and the engine is told by the scheduler to which instance the event is routed.

Both do not require any changed to the BPEL spec, however the b) option which is nicer is somewhat violating the "multiple concurrent receive case".

Mit freundlichen Grüßen
Bernd Eckenfels
Chief Architect
--
SEEBURGER AG - Edisonstr.1 , D-75015 Bretten, Germany
Fax: +49 (0)7252 96-2400 - Phone: +49 (0)7252 96-1256
mailto:b.eckenfels@seeburger.de - http://www.seeburger.de


-----Original Message-----
From: Monica J. Martin [mailto:Monica.Martin@Sun.COM]
Sent: Wednesday, July 28, 2004 10:42 PM
To: ygoland@bea.com; Ron Ten-Hove; Prasad Yendluri
Cc: wsbpel@lists.oasis-open.org
Subject: Re: [wsbpel] Issue - 151 - Allow a new process instance to be
created by "pick onAlarm until"


Yaron Y. Goland wrote:

> I just wanted to go on the record as saying that I believe this 
> feature is an issue for deployment/configuration and therefore out of 
> scope for BPEL. I want to echo Ron's comments that process designers 
> more often than not are not in a position to know what actual values 
> should be used and therefore this is something that should be set at 
> deployment time by the deployment admin.      

mm1: Ron/Yaron/Prasad, then do you have a proposal? Thanks. [1]

[1] Came up on BPEL requirements call today. :-D

>> Issue 151: *Links:* Ugo Corda, 22 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00165.html>     
>> Dieter Koenig1, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00170.html>     
>> Dieter Roller, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00171.html>     
>> Ugo Corda, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00174.html>     
>> Ugo Corda, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00175.html>     
>> Ron Ten-Hove, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00183.html>     
>> Prasad Yendluri, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00184.html>     
>> Prasad Yendluri, 23 Jul 2004 
>> <http://lists.oasis-open.org/archives/wsbpel/200407/msg00184.html>
>> *Changes:* 26 Jul 2004 - new issue
>



To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.