One minor nit... just to be clear that this fault is generated during a subscribe and not later....add "in response to a Subscribe request message" to the end of the new text. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com Gilbert Pilz <gilbert.pilz@oracle.com> Sent by: public-ws-resource-access-request@w3.org 03/10/2009 09:43 PM To "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org> cc Subject Issue 6595: proposal 1 Add the following text to the exposition on /s:Envelope/s:Body/*/wse:Filter after the second paragraph: It is possible for the request to contain a filter that will not evaluate to true for the lifetime of the Subscription. Although this condition cannot be detected for all dialects, implementers are advised to check for it when possible and OPTIONALLY generate a wse:EmptyFilter fault. Add the following fault definition to Section 6: 6.8 EmptyFilter This fault MAY be generated when an Event Source detects a wse:Subscribe request containing a filter that, for whatever reason, will never evaluate to true. [Code] s12:Sender [Subcode] wse:EmptyFilter [Reason] The wse:Filter would result in zero Notifications [Detail] The wse:Filter value.
Received on Wednesday, 11 March 2009 02:24:57 UTC