> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 02, 2004 7:32 PM > To: [EMAIL PROTECTED] > Subject: RE: [portal] Need for CachingPortletAdapter > > > > > > Thanx! > > > > Your PageLabels seem like great enhancement to the portal > engine. Need to > > look closer but > > seems like caching of portlet content will be breeze with > pagelinks in > > use. > > > > But there is one issue remaining. I am afraid that links > don't work on > > first portal page in samples. Seems like pagelinks won't > work on pages > > with no tabs. Did you encounter same behaviour? > > Yes. I suppose that is by design. PageLabels are only > generated for named > items, primarily because items don't have any information to use to > generate a page label. If you have an idea on how that could > be improved > I'd certainly be open to it, although I'm a little unclear on why not > having a page label on a single page web site would be a > problem. Maybe > you could provide an example that would illustrate that. >
If I understood you right, you think that absence of pagelinks (=absence of request param 'pagelink') should be no problem on single page with no tabs. So do I. Or at least at this moment :-) But my position is different. I encountered state when links on first page of portal sample don't work at all. That means, no event as maximalization, close, etc is invoked by clicking on the link on icon. Do I have configured anything wrong or is it a bug? Thank you, Michal
