"Kevin A. Burton" wrote:
>
> So if none of this gets -1 by Monday I am going to make the changes.
>
> - Portlet.init(PortletConfig config) will be removed. It will become
> Portlet.init(). You can get your
> PortletConfig via getPortletConfig(). This is less confusing.
>
+1
> - org.apache.turbine.util.ParameterParser
> - add method getParameterNames() (yes it is a hashtable but... makes
> the API more like servlet)
>
+1
> - PortletConfig:
> - the PortletSet properties will not be bridged. If you set a property
> in the PortletSet then
> it will not be available to a Portlet unless you explicitly
> ask for it.
-1
For most parameters I can think of, the controllers just want the current value for
a given parameter, they don't want to know if it's a locally overridden property
or if it's inherited from the current set. Why would they need to care ?
Do you have an explicit need for querying local only parameters ?
> - getParameters() will return the dynamic Engine (like servlet post)
> parameters.
> - getInitParameters() will return the info in the PortletMarkup
>
+1
> - PortletSet
> - getInitParameters() will return a
> org.apache.turbine.util.ParameterParser which I
> am probably going to rework with getParameterNames()
>
> - getContext() replaced with getPortletSet(). (getContext is a method
> that we might want
> to have in the future..
> - getParameters() will return the Engine's ParameterParser which
> is dynamic.
>
+0. Since I'm going to implement PortletSet as a Portlet, all these calls
will be handled by the PortletConfig associated with the set, but in the
meanwhile it's ok for me.
--
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://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
