W3C home > Mailing lists > Public > public-soap-jms@w3.org > August 2010

Completed ACTION-196 - applied accepted resolutions from last week

From: Eric Johnson <eric@tibco.com>
Date: Mon, 02 Aug 2010 17:58:55 -0700
Message-ID: <4C5769CF.5060507@tibco.com>
To: SOAP-JMS <public-soap-jms@w3.org>
Since this spans a number of issues, it seemed easiest to just capture
the diff output and tag each item with which issue it applies to.

===================================================================
RCS file: /sources/public/2008/ws/soapjms/soapjms.xml,v
retrieving revision 1.94
diff -r1.94 soapjms.xml
601c601
<                                       <p>Specifies the name of the
topic destination to which a response message <rfc2119>SHOULD</rfc2119>
be sent.</p>
---
>                                       <p>Specifies the name of the
topic destination to which a response message will be sent.</p>
604c604
<                                 <p>if the variant is "jndi",
topicReplyToName is not relevant and <rfc2119>MUST</rfc2119> be ignored.</p>
---
>                                 <p>as defined by [<bibref ref='jmsuri'
/>], the topicReplyToName only makes sense if the URI variant is "queue"
or "topic".</p>

Above is for ISSUE-47

1030c1030
<           <item><p>Since the message is already in text format the
"encoding" attribute in the XML header <rfc2119>MUST</rfc2119> be
ignored.</p></item>
---
>           <item><p>Since the message is already in text format the
"encoding" attribute in the XML header has to be ignored.</p></item>

Above is for ISSUE-49

1179,1180c1179
<         <assert class="document" id="Protocol-2034" cr-id=""
preamble="(request-response MEP - requesting node)"> The message
<rfc2119>MUST</rfc2119> be created as a JMS
<         <code>BytesMessage</code> or <code>TextMessage</code> as
defined in <specref ref='binding-message-body'/>.</assert>  </p>
---
>         The message is created as a JMS BytesMessage or TextMessage as
defined in <specref ref='binding-message-body'/>. </p>

Above is for ISSUE-51

1198c1197
<               is the JMS Destination object derived from that name.
Otherwise the implementation must
---
>               is the JMS Destination object derived from that name.
Otherwise the implementation has to

Above is for ISSUE-52

1258c1257
<         "Success" is made.</p>
---
>         "Success" is made, and otherwise transition to "Fail".</p>

Above is for ISSUE-53

1330c1329
<         <tr><td>JMSDeliveryMode</td><td>this <rfc2119>SHOULD</rfc2119>
be the same as that specified on the request</td></tr>
---
>         <tr><td>JMSDeliveryMode</td><td>this ought to be the same as
that specified on the request</td></tr>

Above is for ISSUE-54

1405,1406c1404
<         <p><assert class="document" id="Protocol-2040" cr-id=""
preamble="(one-way MEP - sending node)"> The message
<rfc2119>MUST</rfc2119>
<         be created as a JMS <code>BytesMessage</code> or
<code>TextMessage</code> as defined in <specref
ref='binding-message-body'/>.</assert></p>
---
>         <p>The message is created as a JMS BytesMessage or TextMessage
as defined in <specref ref='binding-message-body'/></p>

Above is for ISSUE-51
Received on Tuesday, 3 August 2010 00:59:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:24 GMT