"Thomas F. Boehme" wrote:
>
> We (IBM) certainly want to get our hands dirty with the customizer.
>
:)
> With regard to multi-threading issues, I think there is more than the
> caching system that needs to audited.
> Santiago removed the RunData from PortletConfig the other day, but there is
> still stuff left in the PortletConfig
> that definitely does not belong there. Stephan Hesmer is looking into that
> right now.
>
Yes it's true. PortletConfig contains contextual informations which have
a different scope form either the request (it may persist between request),
the user session (it may be shared by several sessions) or the portlet
(it will change in the lifetime of the portlet).
One proper way to do it:
- subclass RunData in JetspeedRunData and add the contextual methods
directly in this subclass or in a context object stored in RunData
- when parsing the PSML store all the contexts in the PortletSets
in a Hashtable using the Portlet object as a key.
- in the PortletSet getContent() modify the RunData context before
calling Portlet.getContent().
This require to take some precautions in the RunData modifications and
may impose some change in the PortletControl API (which is the weakest
part of the implementation anyway).
I'll most likely have to do something like this for using templates but
I'm not sure it's doable for a beta next week.
--
Rapha�l Luta - [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]
