With issue 6398 resolved, this issue simply adds more extensibility points to certain transfer messages by changing the "xs:any+" or "xs:any?" to "xs:any*". The following list shows which messages would be impacted. T-GetResponse: <wst:GetResponse ...> xs:any + </wst:GetResponse> change the xs:any+ to xs:any* T-PutRequest: <wst:Put ...> xs:any + </wst:Put> change the xs:any+ to xs:any* T-PutResponse: <wst:PutResponse ...> xs:any ? </wst:PutResponse> change the xs:any? to xs:any* T-DeleteResponse: <wst:DeleteResponse ...> xs:any ? </wst:DeleteResponse> change the xs:any? to xs:any* T-CreateResponse: <wst:CreateResponse ...> <wst:ResourceCreated> xs:any ? </wst:CreateResponse> change the xs:any? to xs:any* By making this change it will allow for extension specifications to have more flexibility in what they send/receive. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.comReceived on Saturday, 28 February 2009 15:16:04 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 3 April 2009 01:27:32 GMT