This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11703 - Eventing: error on bad filter expression
Summary: Eventing: error on bad filter expression
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: CR
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2011-01-09 02:15 UTC by Doug Davis
Modified: 2011-09-13 21:29 UTC (History)
0 users

See Also:


Description Doug Davis 2011-01-09 02:15:13 UTC

Comment 1 Doug Davis 2011-01-09 02:20:32 UTC
Eventing and Enum deal with filters slightly differently.
In particular, enum has this text under the definition of "Filter":
If the data source supports filtering and the requested dialect but cannot process the requested filter content, the request MUST fail, and the data source MUST generate a wsen:CannotProcessFilter fault. 

In cases where the filter expression is bad (e.g. a syntax error) I believe
that the above text in enum will case a wsen:CannotProcessFilter fault
to be generated.  However, I don't see a similar fault defined for eventing.
This leads me to believe that we have an interop issue in the case where
someone provides a bad filter to a Subscribe() because the fault returned
is undefined.

add the above text and corresponding fault to eventing.

Additionally, there's another issue here.  The above fault can only be
generated during subscribe time.  However, not all event sources will
evaluate the expression at that time - some may only do so afterwards
(while processing new events).  Its not clear to me what should happen
in this case.  I'm leaning towards us changing the spec so that when this
happens the Subscription terminates (unexpectedly - e.g. generate an
endSubscription msg) so that the sink knows why its not receiving any
notifications.  But I'd like to discuss this in the group.
Comment 2 Robert Freund 2011-01-25 20:56:23 UTC
remove issue contents after "Additionally"...
Comment 3 Robert Freund 2011-02-01 21:33:26 UTC
resolved as proposed