W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2004

Re: NEW ISSUE: Marking RefProps/RefParams using attributes

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Thu, 2 Dec 2004 13:34:39 -0500
Message-Id: <D3897126-4490-11D9-8692-000A95BD86C0@bea.com>
Cc: "<public-ws-addressing@w3.org>" <public-ws-addressing@w3.org>
To: "Srinivas, Davanum M" <Davanum.Srinivas@ca.com>

Dims,

Perhaps I misspoke; I only wanted to compare the proposals, not raise  
yet another issue. My apologies if I did; in any case, this will fulfil  
your AI nicely. Thanks.

Cheers,


On Dec 1, 2004, at 5:34 PM, Srinivas, Davanum M wrote:

> David,
>
> I don't see it at http://www.w3.org/2002/ws/addr/wd-issues/. Closest
> issue was Glen's i008 and that is for "RefProps/RefParams as individual
> SOAP headers" and Mark I think explicitly mentioned that he wanted to
> compare the two proposals "Marking RefProps/RefParams using attributes"
> vs "RefProps/RefParams as individual SOAP headers". So I sent this as a
> new issue.
>
> Thanks,
> dims
>
> -----Original Message-----
> From: David Orchard [mailto:dorchard@bea.com]
> Sent: Wednesday, December 01, 2004 4:00 PM
> To: Srinivas, Davanum M; public-ws-addressing@w3.org
> Subject: RE: NEW ISSUE: Marking RefProps/RefParams using attributes
>
> Isn't this a new solution, not a new issue?  Seems like it ought to be  
> a
> proposed solution to an existing issue.
>
> Dave
>
>> -----Original Message-----
>> From: public-ws-addressing-request@w3.org
> [mailto:public-ws-addressing-
>> request@w3.org] On Behalf Of Srinivas, Davanum M
>> Sent: Tuesday, November 30, 2004 10:03 AM
>> To: Srinivas, Davanum M; public-ws-addressing@w3.org
>> Subject: RE: NEW ISSUE: Marking RefProps/RefParams using attributes
>>
>>
>> Oops typo in sample....here's the correct one. This completes my
> action
>> item from yesterday.
>>
>> Thanks,
>> dims
>>
>> Complete Sample:
>> <SOAP-ENV:Envelope>
>>      <SOAP-ENV:Header>
>>          <wsa:RefPs soap:mustUnderstand="true"/>
>>          <wsa:MessageID>msgid:1234567902282223</wsa:MessageID>
>>          <wsa:To>http://www.example.com/services/someService</wsa:To>
>>          <wsa:Action>http://www.example.com/someAction</wsa:Action>
>>
> <wsa:From>http://www.example.com/clients/someClient</wsa:From>
>>
>>          ...
>>          <tns:resourceID
>> wsa:type="property">DataChunk42</tns:resourceID>
>>          <tns:expires wsa:type="parameter">32000</tns:expires>
>>      </SOAP-ENV:Header>
>>      <SOAP-ENV:Body>
>>         ...
>>      </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> -----Original Message-----
>> From: public-ws-addressing-request@w3.org
>> [mailto:public-ws-addressing-request@w3.org] On Behalf Of Srinivas,
>> Davanum M
>> Sent: Tuesday, November 30, 2004 1:01 PM
>> To: public-ws-addressing@w3.org
>> Subject: NEW ISSUE: Marking RefProps/RefParams using attributes
>>
>>
>> Title: Marking RefProps/RefParams using attributes
>>
>> Description: As mentioned in several threads, currently there is no
> way
>> to distinguish between regular soap headers and RefProps and RefParams
>
>> just by looking at the soap message on the wire. One could use xml
>> attributes to add extra information on soap headers which have been
>> added ONLY because they were part of the original EPR. This is
> basically
>> to be in tune with the "Self-description" mantra.
>>
>> Justification: Different types of intermediaries can use this
>> information for various purposes (say caching, monitoring,
>> logging/auditing). For example a transparent (does not generate EPR's
>> and is not an endpoint for soap messages) intermediary will be able to
>
>> track all Refp's flowing in the system without a user having to input
>> all QName's being used in the system or use some other out of band
>> mechanism. Another benefit is that one can even use the same QName in
>> both RefParams and RefProps IF we are able to mark them in some
> fashion
>> and we will be able to apply different policies based on whether a
> QName
>> is being used as a RefParam or present in RefProps. We also need a way
>
>> to ensure that attribute is understood by all nodes (and more
>> importantly fail when the soap nodes does not know how to handle
>> RefParams/RefProps attribute stuff)
>>
>> Target: Core
>>
>> Proposal:
>> - SOAP Headers that are added because they were part of an EPR's
>> ReferenceProperties are marked by adding the following attribute:
>> wsa:type="property"
>> - SOAP Headers that are added because they were part of an EPR's
>> ReferenceParameters are marked by adding the following attribute:
>> wsa:type="parameter"
>> - If there's at least one soap header marked with the wsa:type
>> attribute, then add a new header to ensure that the attribute is not
>> ignored silently:
>> <wsa:RefPs soap:mustUnderstand="true"/>
>>
>> Complete Sample:
>> <SOAP-ENV:Envelope>
>>      <SOAP-ENV:Header>
>>          <wsa:ReferenceParameters soap:mustUnderstand="true"/>
>>          <wsa:ReferenceProperties soap:mustUnderstand="true"/>
>>          <wsa:MessageID>msgid:1234567902282223</wsa:MessageID>
>>          <wsa:To>http://www.example.com/services/someService</wsa:To>
>>          <wsa:Action>http://www.example.com/someAction</wsa:Action>
>>
> <wsa:From>http://www.example.com/clients/someClient</wsa:From>
>>
>>          ...
>>          <tns:resourceID
>> wsa:type="property">DataChunk42</tns:resourceID>
>>          <tns:expires wsa:type="parameter">32000</tns:expires>
>>      </SOAP-ENV:Header>
>>      <SOAP-ENV:Body>
>>         ...
>>      </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> Problems:
>> [1] Possible Schema validation problem mentioned by Glen:
>>
> (http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/ 
> 0602.h
>> tml)
>> [2] Possible Signing RefProps/RefParams problem mentioned by Rich:
>>
> (http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/ 
> 0592.h
>> tml)
>>
>> Discussion Threads:
>> [1]
>>
> http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/ 
> thread.
>> html#478
>> [2]
>>
> http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/ 
> thread.
>> html#544
>>
>>
>> Davanum Srinivas
>> Computer Associates
>> Senior Architect, Web Services Group
>> Tel: +1 508 628 8251
>> davanum.srinivas@ca.com
>> http://ws.apache.org/~dims/
>>
>>
>>
>>
>>
>>
>
>
>
>
>

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Thursday, 2 December 2004 18:35:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:00 GMT