I think the portlet name has to only be unique within individual portlet applications. That may have changed though.
*===================================* * Scott T Weaver������������������� * * Jakarta Jetspeed Portal Project�� * * [EMAIL PROTECTED] * *===================================* � > -----Original Message----- > From: David Sean Taylor [mailto:[EMAIL PROTECTED] > Sent: Friday, August 08, 2003 12:03 PM > To: Jetspeed Developers List > Subject: Re: [J2] Classname is not unique enough for PortletCache! > > > On Friday, August 8, 2003, at 06:12 AM, Weaver, Scott wrote: > > > We should probably use the PortletEntity's id as a cache key. > > > > > I believe the spec states "one 'portlet object' by portlet definition", > not one portlet object per entity. > That's why we decided not to use the term "instance" > Instance refers to a Java instance in the spec, not an 'entity' which > is the same as an 'instance' in J1 > > The Portlet name needs to be unique in the descriptor. > I'll add a unique key on the DB and check for a unique key error in the > PAM > > >> > >> The demo application has two portlet with the same classname, > >> CustomerDetail and CustomerInfo. Per PLT.5.1, these are 2 Portlet > >> Instances. > >> > > >> Because they have the same classname and J2's portlet cache uses the > >> classname as the key, then the implementation is treating these two > >> portlets as one instance. > >> > >> This is why the CustomerInfo and CustomerDetail portlet alway return > >> the > >> same content. > >> > >> Who wants to fix this one? > >> > > I'll fix it this morning, thanks for pointing it out > > -- > David Sean Taylor > Bluesunrise Software > [EMAIL PROTECTED] > +01 707 773-4646 > +01 707 529 9194 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
