The following issue has been updated:

    Updater: Jeremy Ford (mailto:[EMAIL PROTECTED])
       Date: Tue, 31 Aug 2004 1:16 PM
    Changes:
             summary changed from JSP Maximizing a Portlet, and navigating away from 
Portlet yields <> in browser to [FIX] JSP Maximizing a Portlet, and navigating away 
from Portlet yields <> in browser
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JS1-514?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS1-514

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS1-514
    Summary: [FIX] JSP Maximizing a Portlet, and navigating away from Portlet yields 
<> in browser
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Jetspeed
 Components: 
             JSP
             Layout
   Fix Fors:
             1.6-dev
   Versions:
             1.5

   Assignee: 
   Reporter: Arthur D'Alessandro

    Created: Fri, 27 Aug 2004 2:00 PM
    Updated: Tue, 31 Aug 2004 1:16 PM
Environment: Tomcat 5.0.19
JVM 1.4.02_04
Windows XPSP2,Linux 2.4


Description:
When maximizing a portlet, and navigating away from the maximized portlet, the new 
page has the layour (header, left and footer), but the portlet space contains:
<></>

I did see postings from 1.4b3, which indicates a possible fix for similar issue, 
however, I'm not sure if the fixes were incorporated, or if this is a different issue

Newsgroup thread (from ~ Feb 2004):
After Maximize Protlet, buildNormalContext not Called

Snipplet from posting:
Boyd, David wrote:
"
...
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.
..."


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to