"Kevin A. Burton" wrote:
>
> //from PortletSet.java
> //WARNING: This is transitional form. The PortletSet is to become itself
> a Portlet
>
> Rapha�l... so what is up with this?
>
See the "Content generation change" thread... :)
I plan to make PortletSet implement the Portlet interface
and instead of setting a controller classname in the PortletSet, associate
a full ControllerClass.
With PortletSet, implementing Portlet, I get a natural way to handle Set-specific
parameters (they just end in the PortletConfig for the Set) and can associate
a PortletControl which may give the user links to customize the set parameters.
Finally, the Screens using the portlets will only have to get the top-level
PortletControl and ask for getContent(). If the control manages a real portlet,
nothing is changed, if it's a PortletSet, the content will actually be generated
by the associated Controller...
In short, if PortletSet implements Portlet, the client will only use the
portlet and portletcontrol API to get content and never deal directly with
Controller.
--
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]
