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 6396 - Transfer-CreateResponse violates WS-I BP
Summary: Transfer-CreateResponse violates WS-I BP
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (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: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 00:02 UTC by Doug Davis
Modified: 2009-03-12 00:20 UTC (History)
1 user (show)

See Also:


Attachments

Description Doug Davis 2009-01-14 00:02:12 UTC
WS-Transfer allows for multiple children in the SOAP Body of the 
CreateResponse message.  The description of the CreateResponse has the 
following (bolding is mine): 
/s:Envelope/s:Body/child::*[position()=2] 

By default, a service MUST return the current representation of the new 
resource as the second child of the s:Body element if the created 
representation logically differs from the representation sent in the 
Create request message.   
... 

Unlike the previous issues, the WSDL/XSD in this case matches the 
normative text. 

WS-I Basic Profile has the following requirement: 
R9981 An ENVELOPE MUST have exactly zero or one child elements of the 
soap:Body element. 

Proposal:
Remove the second child element from the Body of the CreateResponse 
message.
Comment 1 Robert Freund 2009-03-03 12:23:36 UTC
proposed on 2009-02-28 to cwna in http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0152.html
Comment 2 Robert Freund 2009-03-04 12:02:02 UTC
http://www.w3.org/2002/ws/ra/9/03/2009-03-03.html#6396
CWNA