[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue 96 - Proposal For Vote
> Once that happens those semantics can be mapped to BPEL request/responses. This would satisfy the primary issue 96 Isn't there more than that? For example, I imagine we would need to say something about how to identify a particular process instance based on the WS-A information (e.g. by leveraging reference parameters). Ugo > -----Original Message----- > From: Yaron Y. Goland [mailto:ygoland@bea.com] > Sent: Tuesday, May 17, 2005 10:31 AM > To: wsbpeltc > Subject: [wsbpel] Issue 96 - Proposal For Vote > > > I propose we close issue 96 with no action. > > Issue 96 was intended to primarily address the question of > how to handle > asynchronous request/response correlation in BPEL. It also would have > provided a foundation for enabling BPEL to support multi-message > conversation protocols but that was a secondary goal. > > The WS-Addressing WG has taken it as a work item to extend > WSDL 1.1 to > support asynchronous request/response MEPs. The exact method > for doing > this is still to be determined. However whatever they do will enable > WSDL 1.1 to express asynchronous request/response semantics directly. > Once that happens those semantics can be mapped to BPEL > request/responses. This would satisfy the primary issue 96 > was intended > to address. > > Yaron > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS > TC that generates this mail. You may a link to this group > and all your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr oups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]