6395 2009-01-14 00:01:01 +0000 WS-Transfer CreateRequest violates WS-I BP 2009-03-12 00:24:24 +0000 1 1 1 Unclassified WS-Resource Access Transfer FPWD PC Windows XP CLOSED DUPLICATE 6392 http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0004.html P2 normal --- 1 dug ylafon bob public-ws-resource-access-notifications oldest_to_newest 23041 0 dug 2009-01-14 00:01:01 +0000 WS-Transfer allows for multiple children in the SOAP Body of the CreateRequest message. The description of the CreateRequest has the following (bolding is mine): /s:Envelope/s:Body/child::*[position()=1] The first child element of the s:Body element MUST NOT be omitted. The contents of this element are service-specific, and MAY contain the literal initial resource representation, a representation of the constructor for the resource, or other instructions for creating the resource. All other children SHOULD be ignored by the service. 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 CreateRequest message with the WSDL/XSD by removing the text that implies more than one child my appear. 23079 1 dug 2009-01-14 17:39:47 +0000 *** This bug has been marked as a duplicate of bug 6392 ***