First Last Prev Next    No search results available
Details
: Transfer: Add extensibility points for WS-Transfer wrappers
Bug#: 6594
: WS-Resource Access
: Transfer
Status: CLOSED
Resolution: REMIND
: PC
: Windows XP
: FPWD
: P2
: normal
: ---

:
:
: hasProposal
: 6398 6672 6673
:
  Show dependency tree - Show dependency graph
People
Reporter: Doug Davis <dug@us.ibm.com>
Assigned To: Doug Davis <dug@us.ibm.com>
: notifications mailing list ...
:

Attachments


Note

You need to log in before you can comment on or make changes to this bug.

Related actions


Description:   Opened: 2009-02-19 00:12
From:
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0043.html

Once/if we decide on wrappers for the Transfer operations we should
make sure they have proper extensibility points - in particular
modify Transfer as follows:

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.
------- Comment #1 From Robert Freund 2009-03-03 12:27:19 -------
proposed on 2009-02-28 in
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0154.html
------- Comment #2 From Robert Freund 2009-03-17 20:51:00 -------
Action-52
------- Comment #3 From Robert Freund 2009-03-19 09:49:12 -------
Proposal at
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0088.html

First Last Prev Next    No search results available