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 9701 - Eventing: Add a wse:UnsupportedDelivery fault
Summary: Eventing: Add a wse:UnsupportedDelivery fault
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
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
Keywords: externalComments, reviewerSatisfied
Depends on:
Reported: 2010-05-10 20:31 UTC by Antoine Mensch
Modified: 2010-07-28 09:10 UTC (History)
2 users (show)

See Also:


Description Antoine Mensch 2010-05-10 20:31:15 UTC
The spec does not say what happens when the content of the wse:Delivery is not wse:NotifyTo and is not recognized. Per WS-*, unknown extensions should be ignored. However, this may lead to the wse:Delivery element to be considered empty, which is not allowed by the spec. Either a general wse:InvalidSubscription fault should be returned, or, as specific faults for all child elements (EndTo, Format, NotifyTo, Expires, Filter) are already defined, a new one for Delivery should be added.
Comment 1 Li Li 2010-05-12 15:18:08 UTC
The spec says <Delivery> must have at least one child but does not say that child has to be recognized. An unrecognized element still exists and cannot be considered empty in XML 1.0. Therefore, no fault is necessary.
Comment 2 Antoine Mensch 2010-05-12 15:46:40 UTC
OK, maybe my description is not clear. The question should be: what should an event source return in response to a subscribe request containing a wse:Delivery element with unrecognized (and therefore ignored) content? It cannot be a subscription manager endpoint (the subscription is not created), so I guess it should be a fault. Which one? None of the predefined faults seems to apply.
Comment 3 Robert Freund 2010-05-12 18:19:28 UTC
resolved by agreeing to generate a fault when no delivery mechanism has been established.  Editor to supply text
Comment 4 Doug Davis 2010-05-12 18:24:52 UTC
adding new Fault "NoDeliveryMechanismEstablished" with appropriate explanatory text
Comment 5 Robert Freund 2010-05-13 12:52:17 UTC
reviewer satisfied