You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-user@portals.apache.org by Jason Novotny <no...@aei.mpg.de> on 2004/01/07 13:45:26 UTC

another WebSphere migration issue...

    Hi,

    In WebSPhere Portlet API, there is a really nice method available 
from the PortletRequest called getData which returns a PortletData 
object. This a per user customization hashmap essentially that is 
persisted to a database. What should I do to transition code that uses 
PortletData for per user settings to the JSR Portlet model?

    Thanks, Jason

Re: another WebSphere migration issue...

Posted by Jason Novotny <no...@aei.mpg.de>.

Hi Stefan,

    Thanks for the help-- my feeling was that it is PortletPreferences. 
However, I thought these preferences were for everybody like that of 
PortletSettings not per user-- also if users have lots of specialized 
settings, I'm not sure about the performance of sticking this in a 
single XML descriptor vs. a real database.... If I have 50 users with 
customization settings in the CoolPortlet that will be one huge portlet 
descriptor...no?

    Thanks, Jason

Stefan Hepper wrote:

> Hi Jason,
> in the JSR 168 this method is called getPortletPreferences. Basically 
> the WebSphere Portlet API PortletData and PortletSettings are mergend 
> into the PortletPreferences as writeable (PortletData) and read-only 
> (PortletSettings) preferences.
>
> Stefan
>
> Jason Novotny wrote:
>
>>
>>    Hi,
>>
>>    In WebSPhere Portlet API, there is a really nice method available 
>> from the PortletRequest called getData which returns a PortletData 
>> object. This a per user customization hashmap essentially that is 
>> persisted to a database. What should I do to transition code that 
>> uses PortletData for per user settings to the JSR Portlet model?
>>
>>    Thanks, Jason
>>
>>
>
>

Re: another WebSphere migration issue...

Posted by Stefan Hepper <st...@hursley.ibm.com>.

Hi Jason,
in the JSR 168 this method is called getPortletPreferences. Basically 
the WebSphere Portlet API PortletData and PortletSettings are mergend 
into the PortletPreferences as writeable (PortletData) and read-only 
(PortletSettings) preferences.

Stefan

Jason Novotny wrote:

> 
>    Hi,
> 
>    In WebSPhere Portlet API, there is a really nice method available 
> from the PortletRequest called getData which returns a PortletData 
> object. This a per user customization hashmap essentially that is 
> persisted to a database. What should I do to transition code that uses 
> PortletData for per user settings to the JSR Portlet model?
> 
>    Thanks, Jason
> 
>