W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > October 2009

WWW/2002/ws/ra/edcopies wseventing.html,1.104,1.105 wseventing.xml,1.96,1.97

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 20 Oct 2009 23:25:55 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1N0O5T-0006ys-Il@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv26746

Modified Files:
	wseventing.html wseventing.xml 
Log Message:
7553


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -d -r1.96 -r1.97
--- wseventing.xml	20 Oct 2009 23:16:39 -0000	1.96
+++ wseventing.xml	20 Oct 2009 23:25:53 -0000	1.97
@@ -1118,6 +1118,19 @@
     </p>
 
     <p>
+     If the event source chooses not to accept a subscription due
+     to the content of the Subscribe message, then the 
+     event source MUST generate a 
+     SOAP 1.1 Client fault or a SOAP 1.2 Sender
+     fault. If the event source
+     does not accept this subscription due to an internal processing
+     reason and not due to the specific content of the Subscribe
+     message, then the event source MUST
+     generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault
+     which MAY contain the RetryAfter fault detail element.
+    </p>
+
+    <p>
      If the event source accepts a request to create a
      subscription, it MUST reply with a response of the following
      form:
@@ -1189,18 +1202,6 @@
     </p>
 
     <p>
-     If the event source chooses not to accept a subscription due
-     to the content of the Subscribe message, then the 
-     event source MUST generate a 
-     SOAP 1.1 Server fault or a SOAP 1.2 Receiver
-     fault. If the event source
-     does not accept this subscription due to an internal processing
-     reason and not due to the specific content of the Subscribe
-     message, then the event source MUST
-     generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault.
-    </p>
-
-    <p>
      <specref ref="Table4"/> lists another hypothetical request to create a
      subscription.
     </p>
@@ -1385,6 +1386,14 @@
     </p>
 
     <p>
+     If the subscription manager chooses not to renew this
+     subscription, the request MUST fail, and the subscription manager
+     MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault 
+     indicating that the renewal was not accepted. This fault MAY contain
+     the RetryAfter fault detail element.
+    </p>
+
+    <p>
      If the subscription manager accepts a request to renew a
      subscription, it MUST reply with a response of the following
      form:
@@ -1423,13 +1432,6 @@
     </glist>
 
     <p>
-     If the subscription manager chooses not to renew this
-     subscription, the request MUST fail, and the subscription manager
-     MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault 
-     indicating that the renewal was not accepted.
-    </p>
-
-    <p>
      Other components of the outline above are not further
      constrained by this specification.
     </p>
@@ -4583,6 +4585,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553">7553</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -d -r1.104 -r1.105
--- wseventing.html	20 Oct 2009 23:16:39 -0000	1.104
+++ wseventing.html	20 Oct 2009 23:25:53 -0000	1.105
@@ -631,6 +631,17 @@
      a wse:UnusableEPR fault rather than returning the SubscribeResponse 
      message.
     </p><p>
+     If the event source chooses not to accept a subscription due
+     to the content of the Subscribe message, then the 
+     event source MUST generate a 
+     SOAP 1.1 Client fault or a SOAP 1.2 Sender
+     fault. If the event source
+     does not accept this subscription due to an internal processing
+     reason and not due to the specific content of the Subscribe
+     message, then the event source MUST
+     generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault
+     which MAY contain the RetryAfter fault detail element.
+    </p><p>
      If the event source accepts a request to create a
      subscription, it MUST reply with a response of the following
      form:
@@ -671,16 +682,6 @@
        </p></dd></dl><p>
      Other components of the outline above are not further
      constrained by this specification.
-    </p><p>
-     If the event source chooses not to accept a subscription due
-     to the content of the Subscribe message, then the 
-     event source MUST generate a 
-     SOAP 1.1 Server fault or a SOAP 1.2 Receiver
-     fault. If the event source
-     does not accept this subscription due to an internal processing
-     reason and not due to the specific content of the Subscribe
-     message, then the event source MUST
-     generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault.
     </p><p><a href="#Table4">Example 4-1</a> lists another hypothetical request to create a
      subscription.
     </p><div class="exampleOuter">
@@ -827,6 +828,12 @@
      If the subscription is not active, the request MUST fail and the 
      subscription manager MAY generate a wse:UnknownSubscription fault.
     </p><p>
+     If the subscription manager chooses not to renew this
+     subscription, the request MUST fail, and the subscription manager
+     MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault 
+     indicating that the renewal was not accepted. This fault MAY contain
+     the RetryAfter fault detail element.
+    </p><p>
      If the subscription manager accepts a request to renew a
      subscription, it MUST reply with a response of the following
      form:
@@ -848,11 +855,6 @@
         implied start of that duration is the time when the
         subscription manager starts processing the Renew request.
        </p></dd></dl><p>
-     If the subscription manager chooses not to renew this
-     subscription, the request MUST fail, and the subscription manager
-     MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault 
-     indicating that the renewal was not accepted.
-    </p><p>
      Other components of the outline above are not further
      constrained by this specification.
     </p><p><a href="#Table6">Example 4-3</a> lists a hypothetical request to renew the 
@@ -2594,4 +2596,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7478">7478</a></td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7982">7982</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553">7553</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 20 October 2009 23:25:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 October 2009 23:25:57 GMT