- From: Mark Phillips <M8PHILLI@uk.ibm.com>
- Date: Thu, 8 Jul 2010 18:27:23 +0100
- To: public-soap-jms@w3.org
In response to ACTION-188 [1] I have applied the changes to resolve ISSUE-39 [2] as detailed in email: http://lists.w3.org/Archives/Public/public-soap-jms/2010Jun/0030.html The changes affect three areas of the binding specification In Section 2.6.1.2 I changed the definition of the correlated message for the Requesting state. Before: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.86&content-type=text/html;%20charset=utf-8&f=h#rr-requester-request After: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.87&content-type=text/html;%20charset=utf-8&f=h#rr-requester-request In Section 2.6.2.3 I changed the text that describes how to send a correlated response for the Receiving + Sending state. This also changes assertion 2038. Before: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.86&content-type=text/html;%20charset=utf-8&f=h#responder-transition After: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.87&content-type=text/html;%20charset=utf-8&f=h#responder-transition In the same section, in the table "Receiving + Sending State Values", I changed the value for the JMSCorrelationID field to allow for copying JMSCorrelationID to JMSCorrelationID as well as JMSMessageID to JMSCorrelationID. The new assertion 2038 can be seen here: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.87&content-type=text/html;%20charset=utf-8&f=h#Protocol-2038-summary Regards Mark [1] http://www.w3.org/2002/ws/soapjms/tracker/actions/188 [2] http://www.w3.org/2002/ws/soapjms/tracker/issues/39
Received on Thursday, 8 July 2010 17:30:53 UTC