Re: WS-MEX and the transactionality of PutMetadata

Mex says:
        An endpoint MUST reject a PutMetadata request if it is unable to 
process all of the metadata updates requested.

So, its an all or nothing thing - we can make this more elaborate if you 
think we need to.

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Gilbert Pilz <gilbert.pilz@oracle.com> 
Sent by: public-ws-resource-access-request@w3.org
02/13/2011 04:52 PM

To
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
cc

Subject
WS-MEX and the transactionality of PutMetadata






Suppose a MEX consumer sends the following request to a MEX-enabled 
service (SOAP envelope omitted for brevity):

      <mex:PutMetadata>
         <mex:Metadata>
            <mex:MetadataSection Dialect="wsevd:EventDescriptions"
                                 Identifier="
http://www.w3.org/2002/ws/ra/test/scenario">
               <wsevd:EventDescriptions targetNamespace=
"http://www.w3.org/2002/ws/ra/test/scenario"
                                        xmlns:sce=
"http://www.w3.org/2002/ws/ra/test/scenario"
                                        xmlns:wsevd=
"http://www.w3.org/2011/01/ws-evd"
                                        xmlns:xs=
"http://www.w3.org/2001/XMLSchema">

                  ...

               </wsevd:EventDescriptions>
            </mex:MetadataSection>
            <mex:MetadataSection Dialect="wsdl:definitions"
                                 Identifier=
"http://www.w3.org/2002/ws/ra/test/scenario">
               <mex:MetadataReference xmlns:wsa=
"http://www.w3.org/2005/08/addressing">
                  ...
               </mex:MetadataReference>
            </mex:MetadataSection>
         </mex:Metadata>
      </mex:PutMetadata>

and receives a mex:UnsupportedMetadata fault in the response. Further 
Suppose that the [Detail] property of this fault indicates that the 
mex:MetadataReference was the problem. What expectations can the consumer 
have about the state of the EVD contained in the request? In other words, 
are the semantics of PutMetadata "everything succeeds or nothing is 
updated" or simply "some things may have been updated and others may not"? 
I think we need to (a) decide on the semantics and (b) describe them in 
the spec.

~ gp