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 7554 - Eventing: Unsubscribe Fault
Summary: Eventing: Unsubscribe Fault
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Katy Warr
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Reported: 2009-09-09 16:03 UTC by Paul Nolan
Modified: 2009-10-12 21:19 UTC (History)
2 users (show)

See Also:


Description Paul Nolan 2009-09-09 16:03:31 UTC
Section 4.4 Unsubscribe, describes the message to be returned if an Unsubscribe message is accepted. However it does not mention what to return if the Unsubscribe request is not accepted.


Add a new fault to section 6.

6.15 UnableToUnsubscribe

This fault is generated when an unsubscribe request has failed. 
[Code]     s12:Sender
[Subcode]  wse:UnableToUnsubscribe
[Reason]   The Unsubscribe request has failed
[Detail]   none
Comment 1 Li Li 2009-09-16 14:50:24 UTC
just record my comment before forgetting it.

Agree there should be a fault message for Unsubscribe, for example, when the subscription does not exist. 

However, in that case, the fault should be InvalidSubscription as proposed in Issue 7553 [1]. 

If we create an UnableToUnsubscribe fault, it would allow a service to fail a request with any reason beyond the listed ones. If that is the case, should we also add UnableToXXX to each request as well?


Comment 3 Robert Freund 2009-10-02 14:28:48 UTC
consolidated with 7553
Resolution to 7553 will also resolve 7554