Re: [wsrp-webservice] names array in getPortletProperties

[Rich Thompson <richt2@us.ibm.com>]

This is due to names being a top level
item (parameter if this was an operation call). The tested web stacks did
not interoperate well if such a parameter was completely missing from the
message. As a result you will find all such occurrences (e.g. userContext)
require at least one occurrence, though it is nillable.

Rich

Subbu Allamaraju <subbu@bea.com>

11/12/2003 03:17 PM

To	wsrp-webservice@lists.oasis-open.org
cc
Subject	[wsrp-webservice] names array in getPortletProperties

Is there a reason why the schema requires at least
one name (which can 
be nil) in getPortletProperties?

The xsd declares

<element name="names" type="xsd:string" nillable="true"
maxOccurs="unbounded"/>

When the consumer wants to get values for all properties, it could 
simply not add any names, but the schema forces at least one names, so,
a typical request would look like

<urn:getPortletProperties xmlns:urn="urn:oasis:names:tc:wsrp:v1:types">
   <urn:registrationContext>
     <urn:registrationHandle>xyz</urn:registrationHandle>
   </urn:registrationContext>
   <urn:portletContext>
     <urn:portletHandle>abc</urn:portletHandle>
   </urn:portletContext>
   <urn:userContext>
     <urn:userContextKey>joe</urn:userContextKey>
   </urn:userContext>
   <urn:names xsi:nil="true" xmlns:xsi="..."/>
</urn:getPortletProperties>

This seems strange. Did we miss minOccurs="0" from the xsd, or
is there 
a valid reason?

Regards,

Subbu





To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrp-webservice/members/leave_workgroup.php.