Re: [wsbpel] Issue - 264 - <correlationSet> specifications on <invoke>with @initiate="no" & @pattern="response" should be invalid

[Prasad Yendluri <pyendluri@webmethods.com>]

Folks,

So, here is the problem. Alex Previous Stated:

---------------------------------------------------------------------
Hi Prasad,

I am not sure that is an invalid case.
That is more like a valid usecase of check whether the response is consistent with a previously initiated CS. If the response is inconsistent, correlationViolation fault would be thrown.

Similar situation applies to the combination of  @pattern="request" and @initiate="no" on an <invoke>.

An initiated CS serves two functions: (1) message correlation (2) message content consistency

Does it make sense to you?

Thanks!

Regards,
Alex Yiu
-----------------------------------------------------------

So is it the *assumption* then that the message that is the "response" for an <invoke> *will* be delivered to
correct (matching) instance of the process *independent* of  any <CorrelationSet>s that are specified in the message?

If so, where is that stated in the spec?

Or do the usual <CorrelationSet> value matching rules apply for the incoming Message to delivered to the proper instance?
If not,  why not? When it is an asynchronous exchange do we not have the same issue of matching the response of an invoke with correct instance, if correlation sets are not utilized?

In the following example, does the "Invoice" correlation on the response need to match for the message to be delivered ?
We do not state anywhere clearly, on an <invoke> if the <CorrelationSet>s in the reply must match or not for message to be delivered?

This needs to be clarified.

<invoke .....>
	<correlations>
             <correlation set="PurchaseOrder" initiate="yes" 
                          pattern="request"/>
             <correlation set="Invoice" initiate="no" 
                          pattern="response"/>
        </correlations>
</invoke>

Regards,
Prasad

-------- Original Message --------

Subject:	Re: [wsbpel] Issue - 264 - specifications on with @initiate="no" & @pattern="response" should be invalid
Date:	Mon, 17 Apr 2006 16:38:33 -0700
From:	Alex Yiu <alex.yiu@oracle.com>
To:	Danny van der Rijn <dannyv@tibco.com>
CC:	wsbpel@lists.oasis-open.org
References:	20060414114747.CC5B9338AD2@smtp.nildram.co.uk"><20060414114747.CC5B9338AD2@smtp.nildram.co.uk> 444425DA.1090106@tibco.com"><444425DA.1090106@tibco.com>

+1 to Danny. This does not seem to be an issue to me either.

Regards,
Alex Yiu

Danny van der Rijn wrote:

I disagree.  The correlation can be used to enforce a restraint via a correlationViolation fault.

ws-bpel issues list editor wrote:

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 264 - <correlationSet> specifications on <invoke> with @initiate="no" & @pattern="response" should be invalid

Status: received
Date added: 14 Apr 2006
Date submitted: 12 April 2006
Submitter: Prasad Yendluri
Description: The pattern attribute on <correlationSet> specifications is defined for use with the <invoke> activity, to indicate whether the correlation applies to the outbound message (“request”), the inbound message (“response”), or both (“request-response”).

However the specific combination of @pattern="response" and @initiate="no" on an <invoke> should be invalid, as there is no need to supply a correlation set in a reply to an <invoke> if a new correlation set is not being initiated. The reply is automatically correlated with the original invoke and if a new correlation set is not being initiated, it is meaningless to supply a "different" correlation set in the response to the invoke.

In the Examples below (1) is valid but (2) should be invalid.

(1)

<invoke .....>
	<correlations>
             <correlation set="PurchaseOrder" initiate="yes" 
                          pattern="request"/>
             <correlation set="Invoice" initiate="yes" 
                          pattern="response"/>
        </correlations>
</invoke>
  

(2)

<invoke .....>
	<correlations>
             <correlation set="PurchaseOrder" initiate="yes" 
                          pattern="request"/>
             <correlation set="Invoice" initiate="no" 
                          pattern="response"/>
        </correlations>
</invoke>
  

Submitter's proposal:

Clarify that for a <CorreltonSet> specification on <invoke> when the "pattern" attribute has the value "response", the "initiate" attribute can only have the value "yes" .
Changes: 14 Apr 2006 - new issue

---