[
https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl...
]
Adam Kovari commented on GTNPORTAL-3182:
----------------------------------------
I have fixed this in UIPortal.refreshPage() by commenting out code that sets null to
maximized component. BTW I noticed UIPortal has again maximized component field, so now
there are 3 places - UIPage,UIPageBody and UIPortal, maybe this should be unified.
Another problem I discovered was minimizing portlet that got maximized from the producer
portlet using event before. This should work now as well.
Portal 'overriding' maximization of a window in case multiple
portlets on the page receive any event but only one of them changes the portlet window
mode
---------------------------------------------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-3182
URL:
https://issues.jboss.org/browse/GTNPORTAL-3182
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: WebUI
Affects Versions: 3.5.0.Final
Environment: GateIn portal 3.5.0
Reporter: Adam Kovari
Attachments: 00905214-src.zip, case_00903245_using_code_for_case_00905214.ppt,
portal_classic_2013-07-19_14-34-18.zip, portletstates-testcase.zip
1- During the action phase a portlet of the layout (producer) raises an event that
contains both the target portlet reference (portlet ID) and the target window state
desired.
2- The consumer portlets of the event (note: all portlet in the page may not consume the
raised event but only a subset of them will) check if they are the target portlet of the
event. In such a case they change the WindowState to the target state.
3- What we observe is that mechanism works if we have:
- only one consumer on the page
- the consumer is in the last position of the consumer portlets.
Cases where we have multiple consumer on the page and where the target consumer is not
the last in the event consumer list changes the WindowState accoding to command but the
rendering of the portlet does not correspond to the correct state. Typically when we
desire to maximize the portlet the actual WindowState of all portlets are OK (1 portlet is
maximized and others are normal) but the render phase of all portlets are evaluated which
is not the case when you perform a maximize using the WindowState button on the UI or when
the portlet is in the position last from the portlets recieving the event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira