[JBoss JIRA] (GTNPORTAL-3182) 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
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3182:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> 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
12 years, 3 months
[JBoss JIRA] (GTNWCI-50) Deprecate JB7ContainerServlet and enable turning off cross-context logout for AS7 integration
by Marko Strukelj (JIRA)
Marko Strukelj created GTNWCI-50:
------------------------------------
Summary: Deprecate JB7ContainerServlet and enable turning off cross-context logout for AS7 integration
Key: GTNWCI-50
URL: https://issues.jboss.org/browse/GTNWCI-50
Project: GateIn Web Container Integration
Issue Type: Feature Request
Affects Versions: 2.3.1.Final
Environment: JBoss AS7 integration
Reporter: Marko Strukelj
Assignee: Marko Strukelj
Priority: Minor
AS7 integration was initially implemented by using JB7ContainerServlet. Later CatalinaIntegration class was introduced, that has handled the integration logic ever since, making JB7ContainerServlet obsolete. With this change the ability to turn off cross-context logout via servlet context parameter was lost. It would be simple to reintroduce this capability, activating it via system property.
--
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
12 years, 3 months