New Issue: CorrelationSet Consistency Violation. Is this possible?

[Prasad Yendluri <pyendluri@webmethods.com>]

Description:

The specification in section 9.2 states:

"If multiple correlationSet’s are used in a message activity with initiate="no", then the consistency constraint MUST be observed for all correlationSet’s used. For example, the correlationSet's used in an inbound message activity (e.g. <receive>) must all match a message for that message to be delivered to the activity in the given process instance. If one of the initiated correlationSet’s does not match the message, the standard fault bpel:correlationViolation MUST be thrown."

Given  "correlationSet's used in an inbound message activity (e.g. <receive>) must *all* match a message for that message to be delivered to the activity in the given process instance", how is it possible to match up a message with a process instance and throw the "bpel:correlationViolation" exception if "*one* of the correlationSet’s does not match the message" as stated in the last sentence above (excerpt from the from spec).

Minimally this needs some clarification. Off the bat looks to be a contradiction to me.

Regards,
Prasad