RE: [wsbpel] Allowing a new process instance to be created by "pick onAlarm until"

["Ugo Corda" <UCorda@SeeBeyond.com>]

Dieter,
Of course my proposal is not to force you to use a pick to schedule a
process. You would still be able to do it "the normal way" if you want,
using your system management tool. (Not sure what you mean by "normal",
by the way - In BPEL the "normal way" to instantiate a process is for a
partner to send a message to a receive or a pick).

I am proposing to add a capability that would allow process designers to
make the scheduling behavior visible and documented in the process
itself if they so wish.

Ugo

> -----Original Message-----
> From: Dieter Roller [mailto:ROL@de.ibm.com] 
> Sent: Friday, July 23, 2004 12:16 AM
> To: Ugo Corda
> Cc: wsbpel@lists.oasis-open.org
> Subject: Re: [wsbpel] Allowing a new process instance to be 
> created by "pick onAlarm until"
> 
> 
> 
> 
> 
> 
> Ugo,
> 
> I don't think we should go for this feature. Scheduling the 
> execution of programs etc. is typically the responsibility of 
> systems management products. Imbedding scheduling features 
> into BPEL would proliferate the space as a change for 
> scheduling a business process would now require a change in 
> BPEL rather than the normal way (in the systems management tool)...
> 
> Cheers,
> 
> dieter
> 
> 
> 
>                                                               
>              
>              "Ugo Corda"                                      
>              
>              <UCorda@SeeBeyond                                
>              
>              .com>                                            
>           To 
>                                        
> <wsbpel@lists.oasis-open.org>       
>              07/22/2004 11:36                                 
>           cc 
>              PM                                               
>              
>                                                               
>      Subject 
>                                        [wsbpel] Allowing a 
> new process     
>                                        instance to be created 
> by "pick     
>                                        onAlarm until"         
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
> 
> 
> 
> 
> Currently the spec does not allow a Pick with 
> createInstance=yes when alarms are specified. I don't see a 
> good rationale for having this restriction in the case 
> onAlarm specifies a particular time for the associated 
> activities to occur ("until" case).
> 
> Relaxing this restriction would be useful when we want a 
> process instance to start at a particular time, possibly on a 
> periodical base. An alternative way of achieving the same 
> effect would be by defining a receive from a "partner" 
> representing the deployment environment, and having the 
> environment itself send a message at the appropriate time. 
> But I think it would be more clear if we use the pick-onAlarm 
> construct instead.
> 
> Unless somebody shows me that the idea does not make sense, 
> I'll file a formal issue for it.
> 
> Ugo
> 
> 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/le
ave_workgroup.php
.