[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1806) Portlet window state cached when window re-created

Julien Viet (JIRA) jira-events at lists.jboss.org
Fri Nov 16 06:25:18 EST 2007


    [ http://jira.jboss.com/jira/browse/JBPORTAL-1806?page=comments#action_12387903 ] 
            
Julien Viet commented on JBPORTAL-1806:
---------------------------------------

It is a consequence that the window id (because of the same name) is used as cache key, I don't think it can be solved. The only solution would be to use the sequence id of the window as window id instead of the natural id, or combine the window id with something else (like the instance id maybe) as cache key.

> Portlet window state cached when window re-created
> --------------------------------------------------
>
>                 Key: JBPORTAL-1806
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1806
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: JBoss AS 4.0.5 installed with JEMS 1.2.0.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>
> 1. Create a window.
> 2. Minimize it.
> 3. Close the window.
> 4. Re-create the window (exact name, page, coordinates etc).
> 5. Notice that the window is displayed in the minimized view, instead of normal view.
> If you re-login to portal or restart the AS it will work properly (the new window is created in normal view).
> Also note that once a window gets maximized and you re-login/restart the AS the window looses state (is displayed in normal view).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list