Have you activated the portlet cache ? If so, can you try to desactivate the cache and check if you still have this issue ?
What you describe may be a bug in portlet cache left other from the days when portlet did not have any unique ID and the cache was using the parameter list/values to identify the instances... If this is indeed the issue, it should be pretty easy to fix. > -----Message d'origine----- > De : Aurelien Pernoud [mailto:[EMAIL PROTECTED]] > Envoyé : mercredi 16 octobre 2002 14:38 > À : 'Jetspeed Users List' > Objet : RE: Getting Crazy... > > > > I too think there's still bugs in making references to > abstract portlets... > > But the interest is to have a generic portlet and then use > parameters, so > that if you have to update your portlets features, you only > have to change > one class. > > Is a bug report needed ? I don't know what to put in it... > Any jetspeed dev > that knows how the references works can advice ? > > Aurelien > > > -----Message d'origine----- > > De : Brad Straw [mailto:[EMAIL PROTECTED]] > > Envoyé : mercredi 16 octobre 2002 13:40 > > À : "Jetspeed Users List" > > Objet : RE: Getting Crazy... > > > > > > I've never been truly successful in using the same class file > > for multiple portlets as it appears you are attempting here. > > What works for me is simply using unique class files for each > > portlet. So for your "Portlet_Test_AAA" portlet, use > > org.apache.jetspeed.portal.portlets.BugPortletAAA, and for > > "Portlet_Test_BBB" portlet, use > > org.apache.jetspeed.portal.portlets.BugPortletBBB, etc. > > > > Just a thought > > > > > -- > 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]>
