clearly a missing part. Sounds like a good workaround, but maybe we should
address a "more complete" solution in the Portlet API discussion....
But I would appreciate such a solution to handle this problem. It's a mess
that we don't have a good way to transport settings inside of user.psml to
the portlets...
Marcus
> -----Original Message-----
> From: ingo schuster [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 10. November 2000 17:00
> To: JetSpeed
> Subject: User dependent portlet parameters
>
>
> Currently, portlets don't have a possiblility to "behave"
> according to
> parameters that are specific to a certain user. For example: a stock
> watchlist portlet needs to be customizable so that it
> displays those stock
> symbols that the user is interested in.
> Parameters like this could be stored in the <entry> section
> of user.psml as
> name/value pairs. E.g:
>
> <entry type="ref" parent="StockWatchlist">
> <layout position="3"/>
> <parameter name="symbol1" value="SUN"/>
> <parameter name="symbol2" value="IBM"/>
> </entry>
>
> This can already be done today, the parameters also get unmarshaled
> correctly and find their way into the "Protlets-tree".
> However, when the
> PortletSetFactory converts this object tree into a
> "PortletSet-tree", the
> portlet parameters are simply ignored.
> Now, there is actually no good place to put them at the moment:
> PortletConfig shouldn't be user specific as it exists only
> once per portlet
> and PortletControlConfig holds the PortletControl's parameters.
> I think, that if a PortletControl holds a portlet and not a
> PortletSet, it
> should store the portlets (user) parameters and pass them
> along with the
> getContent method.
> In more detail, this could look like follows:
> * A PortletControl has an additional field
> "PortletUserConfig" that holds
> the user-specific portlet settings. PortletUserConfig could
> be a new object
> or just a ParameterParser.
> * When the PortletSetFactory "converts" the "Portlets-tree" into a
> "PortletSet-tree" it takes the portlet parameters and stores
> them in this
> PortletUserConfig.
> * The Portlet's getContent(Rundata rundata) method is changed to
> getContent(Rundata rundata, PortletUserConfig portletUserConfig);
>
> Does this sound sensible?
>
> ingo.
>
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]