- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 06 Mar 2009 22:47:21 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6661
Summary: WS-Eventing Appendix I is incomplete and incorrect
Product: WS-Resource Access
Version: PR
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Eventing
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: gilbert.pilz@oracle.com
QAContact: public-ws-resource-access-notifications@w3.org
Appendix I of the WS-Eventing Member Submission, "Service Metadata for
Eventing", is incomplete in a number of areas. Firstly it does not indicate how
an Event Sink is expected to derive the binding details for the Notifications.
Will the Notifications be sent as RPC/Encoded, Doc/Literal? Will the
Notifications be sent using SOAP 1.1 or SOAP 1.2? Secondly, the relationship
between the "endpoint reference for the event source" and the annotated
portType is unclear. One might think that the "endpoint reference for the event
source" is equivalent to the wsdl:port that implements a binding of the
annotated portType, but this conjecture is not supported by any text or
example.
"Service Metadata for Eventing" is also technically incorrect in that it
requires Event Sources to process a WSDL containing output-only operations in
order to generate the code necessary to correctly process and dispatch
Notification messages which is a violation of BP 1.1 R2303. While one could
argue about the relevance of WS-I profiles to infrastructure-level protocols,
it is clear that creation of Notification handlers is, in this context, an
application-level activity as the type and structure of Notifications is driven
by the application and not WS-Eventing.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Friday, 6 March 2009 22:47:33 UTC