OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrf] Potential incompatibility WS-R / WS-RP

Kirk, nothing in WS-RF has changed with respect to the relationship between
a resource properties document and its resource properties. Since we began
this TC it has been the case that "The complexType defining the resource
properties document MUST define a collection of zero or more child
elements, called resource property elements. Each child element MUST be a
At the recent F2F we simplified what it meant to be a resource properties
document but the requirement for "zero or more" resource properties did not
change. In the case where a WS-Resource has no resource properties and
additionally supports the GetResourcePropertiesDocument operation, then any
GetResourceProperty message would elicit a response of
InvalidResourcePropertyQNameFault. But it should not be the requirement
that a WS-Resource MUST support GetResourcePropertiesDocument as its only
mandatory operation since this may involve the exchange of large XML
documents for some WS-Resources.

Ian Robinson
STSM, WebSphere Messaging and Transactions Architect
IBM Hursley Lab, UK

             "Wilson, Kirk D"                                              
             om>                                                        To 
             17/09/2005 00:46                                           cc 
                                       [wsrf] Potential incompatibility    
                                       WS-R / WS-RP                        

Given the decision in WS-R to separate the resource property document
from resource properties such that a RPDoc MAY contain resource
properties, is there an incompatibility with the following statement in
WS-RP (vers 09, lines 358-360):

Any interface that includes a resource properties document type
declaration (/wsdl:portType/@ResourceProperties) MUST also include the
GetResourceProperty message exchange (operation) defined in this

Should the requirement now that the interface MUST include the

Kirk Wilson
Architect, Development
Office of the CTO
802 765-4337

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]