The following issue has been updated:
Updater: Mark Orciuch (mailto:[EMAIL PROTECTED])
Date: Fri, 2 Apr 2004 10:26 AM
Changes:
assignee changed from Jetspeed Developer Mailing List
description changed from To reproduce that error:
1.Customize your page so that it contains Weather portlet (or any derived) and
at least one other portlet (for more informative example, two others)
2.Click "Minimize" on any non-weather portlet
3.Click "Minimize" on second non-weather portlet
Expected result:
Minimized portlets remain minimized.
Real result:
Previously minimized portlet is displayed in normal mode again. (Alternatively
to minimizing two portlets, you may minimize one, switch to another pane, move
back to the first pane. The results will be identical.)
Here is what I have learned from my investigation:
1. The reason is, that current user's PSML is written by "Minimize" action and
then overwritten with invalid (old) content by buildNormalContext method of
WeatherAction class
2. The line of code that is causing problem:
PortletConfigState.setInstanceParameter(portlet, rundata, WEATHER_CITY_INFO,
cityInfo);
I think that the above line is excessive, and somewhat incompatible
with general JS patterns. to To reproduce that error:
1.Customize your page so that it contains Weather portlet (or any derived) and
at least one other portlet (for more informative example, two others)
2.Click "Minimize" on any non-weather portlet
3.Click "Minimize" on second non-weather portlet
Expected result:
Minimized portlets remain minimized.
Real result:
Previously minimized portlet is displayed in normal mode again. (Alternatively
to minimizing two portlets, you may minimize one, switch to another pane, move
back to the first pane. The results will be identical.)
Here is what I have learned from my investigation:
1. The reason is, that current user's PSML is written by "Minimize" action and
then overwritten with invalid (old) content by buildNormalContext method of
WeatherAction class
2. The line of code that is causing problem:
PortletConfigState.setInstanceParameter(portlet, rundata, WEATHER_CITY_INFO,
cityInfo);
I think that the above line is excessive, and somewhat incompatible
with general JS patterns.
environment changed from Operating System: Windows NT/2K
Platform: PC to Operating System: Windows NT/2K
Platform: PC
priority changed to Blocker
Fix Version changed to 1.5
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JS1-404?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JS1-404
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JS1-404
Summary: [PATCH] Weather portlet influences other portlets' state
Type: Bug
Status: Resolved
Priority: Blocker
Resolution: FIXED
Project: Jetspeed
Components:
Portlets
Fix Fors:
1.5
Versions:
1.4
Assignee:
Reporter: Olaf Romanski
Created: Thu, 30 Oct 2003 8:04 AM
Updated: Fri, 2 Apr 2004 10:26 AM
Environment: Operating System: Windows NT/2K
Platform: PC
Description:
To reproduce that error:
1.Customize your page so that it contains Weather portlet (or any derived) and
at least one other portlet (for more informative example, two others)
2.Click "Minimize" on any non-weather portlet
3.Click "Minimize" on second non-weather portlet
Expected result:
Minimized portlets remain minimized.
Real result:
Previously minimized portlet is displayed in normal mode again. (Alternatively
to minimizing two portlets, you may minimize one, switch to another pane, move
back to the first pane. The results will be identical.)
Here is what I have learned from my investigation:
1. The reason is, that current user's PSML is written by "Minimize" action and
then overwritten with invalid (old) content by buildNormalContext method of
WeatherAction class
2. The line of code that is causing problem:
PortletConfigState.setInstanceParameter(portlet, rundata, WEATHER_CITY_INFO,
cityInfo);
I think that the above line is excessive, and somewhat incompatible
with general JS patterns.
---------------------------------------------------------------------
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]
