RE: [wsrp] getPortletProperties(), desired locale

I think that we said that since these values are normally user specific, even though they CAN be in multiple locales, for each user they will probably only exist in one locale, and therefore the cost of returning all locales is minimal.

Yossi.

From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Thursday, July 15, 2004 4:53 PM
To: wsrp@lists.oasis-open.org
Subject: Re: [wsrp] getPortletProperties(), desired locale

I would say this looks like an item that simply got missed in the v1 API. I suppose the save thing to do it return the property values for all locales since there is no way to indicate the desiredLocales.

Rich

jeff.blattman@sun.com 07/15/2004 00:23 GMT	To	wsrp@lists.oasis-open.org
	cc
	bcc
	Subject	[wsrp] getPortletProperties(), desired locale

This document expires on 10/12/2004

for operations that return localized data, the pattern is to send desired locales as a possible limiter, indicating what locales the consumer is interested in.

the getPortletProperties() operation returns a list of localized property values. said operation is not passed the desired locales. in the case when there is a jsr-168 portlet behind the wsrp portlet, it is possible for the jsr-168 portlet to have multiple localized preference values for a given preference name (see PLT.14.3.1 in the 1.0 portlet spec).

is getPortletProperties() expected to return multiple localized values for a given property name?

if so, why does this operation not accept desired locales?

if not, how does the producer choose which localized values to send back?

thanks.

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/members/leave_workgroup.php.
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/members/leave_workgroup.php.

wsrp message