ingo schuster wrote:
>
> > >
> > > good, but perhaps we can derive RunData to JetspeedRunData and include the
> > > needed data there. The JetspeedRunData idea was mentioned from Raphael to
> > > solve problems with request-sensitive data in PortletConfig.
> > >
> >
> >The parameter bug was fixed yesterday.
> >
> >Also, whatever system you chose for storing the PSML-related informations,
> >I'll most probably need to subclass RunData for keeping the template
> >related informations, so I think we should also use it for the PSML-related
> >stuff too.
>
> Ok, we can also subclass RunData and provide a PortletUserConfig field
> there. I don't like the idea that this field will be set for every
> getContent call so much (this makes it essentially an indirect parameter
> passing), however I can see that we save work if we leave the
> getContent(RunData) signature unchanged.
>
I don't like this way of doing things very much, but it's the Turbine way and
it is silly to use a framework and not conform to its design philosophy...
--
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]
