7205 2009-08-03 15:23:20 +0000 Eventing: Fault behavior for delivery element (6692-b) 2015-06-20 16:35:07 +0000 1 1 1 Unclassified WS-Resource Access All FPWD All All CLOSED REMIND http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0050.html P2 normal --- 1 lli5 public-ws-resource-access-notifications dug public-ws-resource-access-notifications oldest_to_newest 26195 0 lli5 2009-08-03 15:23:20 +0000 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. 26248 1 bob 2009-08-05 21:31:04 +0000 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. 121281 2 jackiewindsor09 2015-06-20 16:34:18 +0000 Please make my changes 121361 3 jackiewindsor09 2015-06-20 16:35:07 +0000 Please make my changes