I can describe very easily how it works:
You basically have 4 types of layout elements:
Portlet = Component
PortletSet = Container
PortletController = LayoutManager
PortletControl = decorator (specialized container, handled more or less
like insets are used in AWT))
When you call a page, Jetspeed reads the associated PSML page and builds
a tree of PortletSet and Portlet. However for each Portlet or PortletSet, if
there's a PortletControl associated it is instanciated instead as a Proxy to
the
real Portlet or Set
Whenever a Page needs to be rendered, the engine walks the tree to render
each
Portlet or portletSet individually.
Whenever a PortletControl needs to be rendered, it handles its layout
function
(like providing title bars) and then invokes the proxied Portlet or
PortletSet
rendering.
Whenever a PortletSet needs to be rendered, the PortletSet delegates the
actual layout management to an associated Controller (Strategy pattern).
Whenever a simple Portlet is rendered, it does whatever it wants :)
--
Rapha�l Luta - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
> -----Message d'origine-----
> De : Jason Novotny [mailto:[EMAIL PROTECTED]]
> Envoy� : jeudi 12 septembre 2002 18:51
> � : jetspeed-dev
> Objet : portlet controllers
>
>
>
> Hi,
>
> I'm trying to better understand how the portlet layout works in
> Jetspeed. Is there any documentation on this? In particular I
> see some
> file called controllers.xreg which seems to have info on various
> PortletControllers-- how does this get instantiated/loaded if
> at all by
> Turbine.java or the "portlet container"? Any other info,
> especially some
> kind of sequence diagram or explanation in that format would be very
> helpful to me.
>
> Thanks very much, Jason
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
