ServiceGroup Proposal for WSRF44. Monday, March 21 st , 2005. Tom Maguire (IBM). Issue WSRF44. Issue WSRF44: No obvious mechanism to include only members which extend a certain interface
ServiceGroup Proposal for WSRF44
Monday, March 21st, 2005
Tom Maguire (IBM)
Issue WSRF44: No obvious mechanism to include only members which extend a certain interface
The method of aggregation for WSDL 1.1 required by WS-ResourceProperties allows only a single portType to be exposed by a WS-Resource. This has the consequence of restricting the value of the MemberInterface attribute of the membershipContentRule to having 1 value. It does not appear possible to specify a ServiceGroup that contains only members that have extended from a specific interface.
Membership constraints are only normatively defined for portType QName matching.
WS-ResourceProperty approach in WSDL1.1 obfuscates all but the most derived portType
ContentElements="list of QName“
MemberInterface- specifies the members to which this MembershipConentRule applies according to the interface (WSDL 1.1 portType) of the member Web service. There must be at most one MembershipContentRule for any given value of @MemberInterface.
ContentElements - specifies the content restrictions according to the list of QNames, each of which refer to a XML Schema global element declaration. This list defines the constraints on the wssg:Content resource property of the ServiceGroupEntry that must be satisfied for membership. The list may be an empty list. An empty list places no content constraints on the resource properties of the ServiceGroupEntries that match the enclosing MembershipContentRule.
<wssg:MembershipContentRule ContentElements="list of QName“>
<memberConstraint context=“anyURI“ selector=“list of QName”/>?
@ContentElements – Same as previous MembershipContentRule
memberConstraint - specifies the member matching constraints for the group.
[email protected] – Extensible URI for establishing contexts for evaluation of @selector attribute.
[email protected] – based on context URI
Today as normatively described limited to WSDL1.1
Enhancement using a context of WSDL1.1
Enhancement using a context of WSDL2.0
Members must have RP document with a RPE of wsdm:ResourceId which infers that the WS-Resource extends the wsdm:Indentification portType.