[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Incorrect conflictingRequest definition?
Hi Ugo, I think you are right, it should have read: "...on the same partnerLink, portType, operation and messageExchange tuple..." This is what the resolution of 123 states: "It is illegal to have multiple simultaneous open IMAs, which have the same partnerLink, operation and messageExchange tuple. A BPEL process MUST throw a bpws:conflictingRequest fault when the conflicting IMA begins execution." Rgds, -----Original Message----- From: Ugo Corda [mailto:Ugo.Corda@Sun.COM] Sent: Monday, February 06, 2006 2:09 PM To: wsbpel@lists.oasis-open.org Subject: [wsbpel] Incorrect conflictingRequest definition? In Appendix A, Table A.1. Standard Faults, I find the following definition: <<conflictingRequest: Thrown when more than one synchronous inbound request on the same partner link for a particular port type, operation and correlation set(s) are active>>. This does not look correct. In particular, it does not even mention the constraint on messageExchange values being the same. Ugo --------------------------------------------------------------------- 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_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]