DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24242>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24242 Weather portlet influences other portlets' state Summary: Weather portlet influences other portlets' state Product: Jetspeed Version: 1.4b5-dev / CVS Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Minor Priority: Other Component: Portlets AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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 unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
