- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 25 Feb 2009 22:30:23 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6400
Wu Chou <wuchou@avaya.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wuchou@avaya.com
--- Comment #1 from Wu Chou <wuchou@avaya.com> 2009-02-25 22:30:23 ---
Doug,
Our understanding to your proposal is: it intends to propose a BP compliant
(e.g. reverse into in-only at client) alternative of Eventing. It is not to
eliminate the SubscriptionEnd function of Eventing.
The SubscriptionEnd is a critical function of Eventing for server to notify the
subscriber that its subscription has ended un-expectedly. Without it, client is
totally in the dark, when the eventing service needs to end unexpectedly.
Please confirm if our understanding to your proposal is correct.
- Wu Chou.
(In reply to comment #0)
> WS-Eventing defines an output-only operation:
> <wsdl:portType name="EventSource" >
> ...
> <wsdl:operation name="SubscriptionEnd" >
> <wsdl:output
> message="wse:SubscriptionEnd"
> wsa:Action="
> http://schemas.xmlsoap.org/ws/2004/08/eventing/SubscriptionEnd"/>
> </wsdl:operation>
> </wsdl:portType>
> WS-I Basic Profile R2303 says the following:
> 4.5.2 Allowed Operations
> Solicit-Response and Notification operations are not well defined by WSDL
> 1.1; furthermore, WSDL 1.1 does not define bindings for them.
> R2303 A DESCRIPTION MUST NOT use Solicit-Response and Notification type
> operations in a wsdl:portType definition.
> Proposal:
> Remove this operation.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 25 February 2009 22:30:33 UTC