Re: [service-orientated-architecture] Modelling Waits (was Orchestration, Choreography, and Composition)

[Ashley at Metamaxim]

Dear All   I think that the "wait" issue raised by Todd in his post on definitions is an interesting one.   Here is a little example which seems quite nasty when you try to model the "waits":   The XYZ company offers a service for its customers to buy products. To use this service, a customer has to invoke three operations in turn:   - PlaceOrder - ConfirmOrder - Pay   An arbitrary time can elapse (e.g., several days) between the invocation of each.   At any time during this, the customer can invoke:   - Cancel   to cancel the order.   Within XYZ, handling PlaceOrder is a manual process that requires the following to be done:   - ConfirmCustomerCredit - ConfirmStockAvailability - CalculateOrderPricing   These three are handled as manual internal processes by XYZ, in parallel. Because they are complex processes requiring specialist skills, each can also sometimes take several days to complete. While they are in progress (i.e., until all three have been completed), the customer is blocked from invoking the ConfirmOrder operation, but can Cancel.   What does the process for this service look like (say in BPEL)? When I try it (using PICK for all the events, including the completion of the internal processes), it gets complicated -- more complicated than I think it should be.   Anyone up for trying it?   Rgds Ashley __._,_.___ SPONSORED LINKS Computer software Computer aided design software Computer job Soa Service-oriented architecture YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___