[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]