Proposed resolution for Issue 38 (ACTION-182)

The following is a proposal in response to
http://www.w3.org/2002/ws/soapjms/tracker/issues/39 .  This completes
ACTION-182.

The binding specification needs the following modifications:


In Section 2.6.1.2, the sentence: "A correlated response message is one
where the value of the JMSCorrelationID header field is the same as the
value of the JMSMessageID of the request message."
becomes:
"If the JMSCorrelationID header field is set in the request message then a
correlated response message is one where the value of the JMSCorrelationID
header field is the same as the value of the JMSCorrelationID of the
request message.  If the JMSCorrelationID header field is not set in the
request message then a correlated response message is one where the value
of the JMSCorrelationID header field is the same as the value of the
JMSMessageID header of the request message."


In Section 2.6.2.3, the sentence:  "The value of the JMSCorrelationID
header field MUST  be set to the same as the value of the JMSMessageID of
the request message."
becomes:
"If the JMSCorrelationID is set in the request message, then the
JMSCorrelationID header field in the response message MUST be set to the
same value as the JMSCorrelationID header field in the request message.  If
the JMSCorrelationID header field is not set in the request message, then
the JMSCorrelationID header field in the response message MUST be set to
the value of the JMSMessageID header in the request message."
(this replacement text becomes the new protocol-2038)


Also in Section 2.6.2.3 in the "Receiving + Sending State Values" table,
the value column for the "JMSCorrelationID" row, changes from:
"this is copied from the request JMSMessageID"
to:
"this is copied from the request JMSCorrelationID if it is set, or the
request JMSMessageID if the request JMSCorrelationID is not set"


Regards
Mark

Received on Wednesday, 23 June 2010 10:00:35 UTC