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 7205 - Eventing: Fault behavior for delivery element (6692-b)
Summary: Eventing: Fault behavior for delivery element (6692-b)
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: All (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-03 15:23 UTC by Li Li
Modified: 2015-06-20 16:35 UTC (History)
1 user (show)

See Also:


Attachments

Description Li Li 2009-08-03 15:23:20 UTC
Issue:
When Qnames are used for delivery mode extension, there are situations that the event source cannot support the requested delivery mode extension of the event subscriber. Therefore, there is a critical need to define the fault behavior when such situation occurs. 

Proposal:
We propose to use delivery policy to decorate the delivery mode extension and using the WS-Policy standard fault mechanism to define the fault behavior for the delivery mode extension. Detailed proposal is described in (Section B.3) http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0050.html.
Comment 1 Robert Freund 2009-08-05 21:31:04 UTC
Resolved with:
There are two faults defined. The current fault that indicates internal error, and a fault that replaces the invalidmode fault that indicates subscribeRequestInvalid the detail elements of both of these fault would be implementation dependent both faullts are "generated" and not necessarilly "transmitted". The <wse:RetryAfter> element would be retained.  Text that describes the generation of these faults in the body of the spec will need to be adjusted accordingly.
Comment 2 Jackie 2015-06-20 16:34:18 UTC
Please make my changes
Comment 3 Jackie 2015-06-20 16:35:07 UTC
Please make my changes