We are seeing this problem in JS 1.5, does anyone have a bug to reference? I did not see any open or closed issues resembling this post. Does anyone have a workaround. This is the issue ASturtz posted subject 'Portlet state problem' this afternoon. -Art ------------------------------------------------------------------------- From: Dmitry Sklyut Subject: RE: After Maximize Protlet, buildNormalContext not Called Date: Thu, 12 Feb 2004 06:39:41 -0800 That is what I saw also. Handling of the js_peid is not consistent as well as handling of "template". They just don't get reset correctly.
This is still a problem in b4 and 1.4 final. Dmitry -----Original Message----- From: Boyd, David [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 9:36 AM To: 'Jetspeed Users List' Cc: Dmitry Sklyut Subject: RE: After Maximize Protlet, buildNormalContext not Called After further investigation, your comments make sense. There seems to be a bug in the way Jetspeed 1.4b3 handles a portlet when it is maximized, restored or minimized. After digging around and outputting rundata, saw that when you maximized a portlet, the js_peid is set to the portlet that is maximized. When you then select a link off of that page to go to a completely different psml, the Jetspeed:pane tag lib is called, it checks to see if the js_peid is set, if so, then it uses that value to look for a portlet in the psml file, if it is not set then it uses the name to locate the portlet. Since the psml does not have any portlets with that js_peid, we get the blank screen. The solution was to modify the MAXIMAZE, RESTORE and MINIMIZE classes along with the pane taglib class. Added a new key,value pair to the temp storage to control the behavior. ---------------------------------------------------- This mailbox protected from junk email by Matador from MailFrontier, Inc. http://info.mailfrontier.com <http://info.mailfrontier.com/> -----Original Message----- From: Dmitry Sklyut [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 5:42 PM To: 'Jetspeed Users List' Subject: RE: After Maximize Protlet, buildNormalContext not Called I saw that happen with forwards that forwarded to a pane. All works fine if forwarded to a portlet. I think it happens because rundata keeps the old js_peid and tries to render the portlet with that old js_peid. Dmitry -----Original Message----- From: Boyd, David [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 5:39 PM To: Jetspeed Users List Subject: After Maximize Protlet, buildNormalContext not Called I have a page where there are 2 columns of 5 rows of portals. If a user maximizes a given portlet, and then selects a link from that portlet, the user is taken to the correct page, as indicated by the URL, but no content is displayed except for the following "<></>". If the user navigates back to the original page, selects the restore icon, then selects same link on the same portlet, the user is taken to the same page, but, now there is content. Any ideal as to why this occurs. _____ This mailbox protected from junk email by Matador from MailFrontier, Inc. http://info.mailfrontier.com <http://info.mailfrontier.com/> <http://info.mailfrontier.com <http://info.mailfrontier.com/> >
