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 6727 - Eventing: Missing Body on UnsubscribeResponse
Summary: Eventing: Missing Body on UnsubscribeResponse
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-03-24 00:54 UTC by Doug Davis
Modified: 2009-05-27 04:05 UTC (History)
1 user (show)

See Also:

Attachments

Description Doug Davis 2009-03-24 00:54:33 UTC 
UnsubscribeResponse message has no Body defined.
For consistency and extensibility we should add one.

Proposal:
Add:
<wse:UnsubscribeResponse ...>
  xs:any *
</wse:UnsubscribeResponse>

to the Body of the UnsubscribeResponse message.
Comment 1 Ram Jeyaraman 2009-04-07 20:19:43 UTC 
The issue/proposal is reasonable. The following changes [1] [2] to XSD and WSDL are needed. We will not propose this to the WG but rather action the issue originator to propose the necessary changes so we can review.

[1] XSD changes

  <!-- Unsubscribe response -->
  <xs:element name="UnSubscribeResponse">
    <xs:complexType>
      <xs:sequence>
        <xs:any namespace="##other" processContents="lax" 
                minOccurs="0" maxOccurs="unbounded" />
      </xs:sequence>
      <xs:anyAttribute namespace="##other" processContents="lax" />
    </xs:complexType>
  </xs:element>

[2] WSDL changes

  <wsdl:message name="UnsubscribeResponseMsg">
    <wsdl:part name="body" element="wse:UnsubscribeResponse" />
  </wsdl:message>
Comment 2 Robert Freund 2009-04-07 20:20:45 UTC 
resolved with comment #1