On Fri, 10 May 2002, Endre Stolsvik wrote: > Have you read and analysed the "new API", and preferrably also the "Portlet > Programming Guide" for IBM's _new-new_ version of the Jetspeed API? Because > that's the whole idea in both of those, but read my earlier emails. I would > love if Rapahel Luta would comment too.. > > There is a concept of a Portlet class instance (which there are only one if, > confer Servlets). Then, portlet class instance + PortletSettings object make > up the Concrete Portlet. Portlet Settings are parameters from the > administartor. He might make several PortletSettings objects with different > parameters, thus making several concrete portlets from one portlet. (And > mind you, you might also make several Portlets from one class file, as you > can with Servlets). > > Then, concrete portlet + PortletData makes the Concrete Portlet Instance. > PortletData is per-user-per-page data (I think..?). The PortletData can only > be changed by the portlet itself. The Concrete Portlet Instances "lives" on > the pages of user, obviously.. > > Then, concrete portlet instance + PortletSession makes User Portlet > Instance. This is "one servicing" of a portlet. The PortletSession stores > transient data used for ONE rendering of the portlet.
About time, too! - portlet encapsulation is such a fundamentally good idea, it's amazing that the APIs have taken so long to get there. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 [EMAIL PROTECTED] "Roger Penrose can never be convinced that this sentence is true." (If he doesn't get the joke, you can at least prove that he owes you money.) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
