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 7553 - Eventing: GetStatus Fault messages
Summary: Eventing: GetStatus Fault messages
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 15:58 UTC by Paul Nolan
Modified: 2009-12-08 22:17 UTC (History)
2 users (show)

See Also:

proposal for 7553/4 (462.00 KB, application/msword)
2009-10-02 11:08 UTC, Katy Warr
Updated proposal based on discussions (463.00 KB, application/msword)
2009-10-02 14:42 UTC, Katy Warr

Description Paul Nolan 2009-09-09 15:58:56 UTC
Section 4.3 GetStatus describes what to do if a subscription is valid and not expired. However it makes no mention of what to do otherwise.


Add two new faults to section 6.

6.13 InvalidSubscriotion

This fault is generated when a request specifies a subscription that is not valid

[Code]      s12:Sender
[Subcode]   wse:InvalidSubscription
[Reason]    The subscription is not valid
[Detail]    none

6.14 SubbscriotionExpired

This fault is generated when a request specifies a subscription that has expired

[Code]     s12:Sender
[Subcode]  wse:SubscriptionExpired
[Reason]   The subscription has expired
[Detail]   none
Comment 2 Katy Warr 2009-10-02 11:08:13 UTC
Created attachment 769 [details]
proposal for 7553/4

- Add definition of subscription to the terminology section
- Before that active state exists, the renew req, get_status req, unsubscribe req must fail and may generate the invalid subscription fault. 
- Tidy the language in get status which suggests that there is a difference between expired and invalid

- Changed InvalidSubscrption to UnknownSubscription throughout
- Remove SubscribeRequestInvalid, EventSourceUnableToprocess,UnableToRenew, InvalidMessage and references to them.
-Should make it clear where to put the retry in the generic fault - i.e. that it can be used in the detail space
Comment 3 Katy Warr 2009-10-02 14:42:08 UTC
Created attachment 770 [details]
Updated proposal based on discussions
Comment 4 Robert Freund 2009-10-20 20:02:49 UTC
Resolved as proposed updated with text at