New issue: Inconsistent definitions of conflictingRequest

["Ugo Corda" <Ugo.Corda@Sun.COM>]

The latest draft contains 3 definitions of conflictingRequest:

Sec. 10.4:

"The correlation between a request and the corresponding reply is based
on the constraint that more than one outstanding synchronous request
from a specific partner link for a particular portType, operation and
correlation set(s) MUST NOT be outstanding simultaneously. If this
constraint is violated during execution, then the standard fault
bpws:conflictingRequest MUST be thrown by a compliant implementation". 

[...]

"If there should ever be multiple simultaneous incomplete inbound
message activities which have the same partnerLink, operation and
messageExchange tuple then the bpws:conflictingRequest fault MUST be
thrown within the BPEL process on the conflicting inbound message
activities subsequent to the execution of the successful incomplete
receive".


Appendix A:

"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". 


According to my understanding, the second definition is the correct one.


Ugo