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 6394 - WS-Transfer PutResponse violates WS-I BP
Summary: WS-Transfer PutResponse violates WS-I BP
Status: CLOSED DUPLICATE of bug 6392
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Yves Lafon
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:00 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:00:15 UTC
WS-Transfer allows for multiple children in the SOAP Body of the 
PutResponse message.  The description of the PutResponse has the following 
(bolding is mine): 
/s:Envelope/s:Body/child::*[position()=1] 

By default, a service MUST return the current representation of the 
resource as the initial child of the s:Body element if the updated 
representation differs from the representation sent in the Put request 
message.  The presence of additional child elements which contain other 
information pertaining to the update is service-specific. 

The implication is that multiple children may appear.  The WSDL/XSD only 
allows for one child though. 

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:
Align the text of the PutResponse message with the WSDL/XSD by removing 
the text that implies more than one child my appear.
Comment 1 Doug Davis 2009-01-14 17:39:35 UTC

*** This bug has been marked as a duplicate of bug 6392 ***