Issue - 236 - Clarification on CorrelationViolation for Outbound Messages

Hello Alexandre,

 

just a minor note, i think we had this already, but since 
we want to change the wording here: if a reply is received on a two way invoke, 
and the reply violates the correlation, then the message will not be dispatched 
(this issue) and a correlation violation will be thrown by the invoke - however, 
it is not required (but possible?) to be also send to the web service who 
originated the response?

 

I also think the below proposed changes to the appendix are 
not correct, or do you really want to receive the reply if it violates the 
"in"-constraint?

 

Thrown when the contents of the messages that are processed in an 
  invoke, receive, or reply activity do not match specified correlation 
  information. If the fault is in the context of an inbound message, then the 
  message MUST not be received by the process, except in the case of an 
  invoke activity with a request/reply operation. If the fault is in 
  the context of an outbound message, then the message MUST NOT be dispatched by 
  the process. 

 

Gruss

Bernd

 

From: ws-bpel issues list editor 
[mailto:] 
Sent: Wednesday, November 23, 
2005 5:14 PM
To: 
Subject: 
[wsbpel] Issue - 236 - Clarification on CorrelationViolation for Outbound 
Messages

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 - 236 - Clarification on CorrelationViolation for Outbound 
MessagesStatus: received
Date added: 23 Nov 
2005
Categories: Correlation
Date submitted: 23 
November 2005
Submitter: Alexandre 
Alves
Description: 

Specification does not clarify what happens when a invoke activity fails with 
bpws:correlationViolation fault for the out message (i.e. pattern out or 
out-in). Is the request actually send out or not?
Submitter’s 
proposal: 

In the case of the correlationViolation failure for the outbound message, the 
message is not dispatched out. 

- In section 14.3 Correlation, replace the paragraph: 

If the correlation set is already initiated and the initiate 
  attribute is set to "no", the correlation consistency constraint MUST be 
  observed. An inbound message cannot be received unless it matches the stated 
  correlation set. Though there is one exception; an inbound message will be 
  received in the case of an <invoke> with a request/reply operation even 
  if the reply does not match the stated correlation set. In this case 
  bpws:correlationViolation MUST be thrown by a compliant implementation. If the 
  correlation set does not match an outbound message then the standard fault 
  bpws:correlationViolation MUST be thrown by a compliant implementation. 

by: 
If the correlation set is already initiated and the initiate 
  attribute is set to "no", the correlation consistency constraint MUST be 
  observed. An inbound message cannot be received unless it matches the stated 
  correlation set. Though there is one exception; an inbound message will be 
  received in the case of an <invoke> with a request/reply operation even 
  if the reply does not match the stated correlation set. In this case 
  bpws:correlationViolation MUST be thrown by a compliant implementation. If the 
  correlation set does not match an outbound message then the standard fault 
  bpws:correlationViolation MUST be thrown by a compliant implementation and 
  the outbound message MUST NOT be dispatched by the process. 

- In Appendix A. Standard Faults, replace the paragraph: 

  
Thrown when the contents of the messages that are processed in an invoke, 
  receive, or reply activity do not match specified correlation information. 

by: 

Thrown when the contents of the messages that are processed in an 
  invoke, receive, or reply activity do not match specified correlation 
  information. If the fault is in the context of an inbound message, then the 
  message MUST not be received by the process, except in the case of an invoke 
  activity with a request/reply operation. If the fault is in the context of an 
  outbound message, then the message MUST NOT be dispatched by the process. 

Changes: 23 Nov 2005 - new issue

To comment on this issue (including whether it should be accepted), please 
follow-up to this announcement on the  list (replying 
to this message should automatically send your message to that list), or ensure 
the subject line as you send it starts "Issue - 236 - [anything]" or is a 
reply to such a message. If you want to formally propose a resolution to an open 
issue, please start the subject line "Issue - 236 - Proposed resolution", 
without any Re: or similar. 

To add a new issue, see the issues procedures document (but the address for 
new issue submission is the sender of this announcement). 

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