July 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNWSRP-370) Status of whether calling modifyRegistration is needed gets de-synchronized

by Chris Laprun (JIRA)

Chris Laprun created GTNWSRP-370: ------------------------------------ Summary: Status of whether calling modifyRegistration is needed gets de-synchronized Key: GTNWSRP-370 URL: https://issues.jboss.org/browse/GTNWSRP-370 Project: GateIn WSRP Issue Type: Bug Security Level: Public (Everyone can see) Components: Admin GUI, Consumer Affects Versions: 2.2.10.Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.2.11.Final -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3145) Add possibility to specify extensions folder from a configuration property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3145?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3145: ---------------------------------------------------- Lucas Ponce <lponce(a)redhat.com> made a comment on [bug 920553|https://bugzilla.redhat.com/show_bug.cgi?id=920553] Domain demo documentation updated: https://github.com/gatein/gatein-portal/tree/master/packaging/jboss-as7 Major limitation is about deployment extensions, that they have to be deployed in a manual way. But with GTNPORTAL-3145 now extensions can be configured per server or server group, having possibility to personalize multitenancy infraestructures with JPP and Domain mode. > Add possibility to specify extensions folder from a configuration property > -------------------------------------------------------------------------- > > Key: GTNPORTAL-3145 > URL: https://issues.jboss.org/browse/GTNPORTAL-3145 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Marko Strukelj > > This feature can help in domain mode to specify different extensions per server groups. -- 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, 9 months

1
0
0 / 0

[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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3182: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=984405 > 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: 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, 9 months

1
0
0 / 0

[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 Adam Kovari (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ] Adam Kovari updated GTNPORTAL-3182: ----------------------------------- Attachment: portletstates-testcase.zip Reproducer > 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: 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, 9 months

1
0
0 / 0

[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 Adam Kovari (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ] Adam Kovari updated GTNPORTAL-3182: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/578 > 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: 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, 9 months

1
0
0 / 0

[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 Adam Kovari (JIRA)

Adam Kovari created GTNPORTAL-3182: -------------------------------------- Summary: 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 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3180) portal-redirects element not in gatein_objects XSD

by Matt Wringe (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3180?page=com.atlassian.jira.pl... ] Matt Wringe updated GTNPORTAL-3180: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/577 > portal-redirects element not in gatein_objects XSD > -------------------------------------------------- > > Key: GTNPORTAL-3180 > URL: https://issues.jboss.org/browse/GTNPORTAL-3180 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Nick Scavelli > Assignee: Matt Wringe > > portal-redirects element and it's children are not present in gatein_objects XSD. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3181) Responsive Skin: select page dialog overflow

by Matt Wringe (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3181?page=com.atlassian.jira.pl... ] Matt Wringe updated GTNPORTAL-3181: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/576 > Responsive Skin: select page dialog overflow > -------------------------------------------- > > Key: GTNPORTAL-3181 > URL: https://issues.jboss.org/browse/GTNPORTAL-3181 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matt Wringe > > see https://bugzilla.redhat.com/show_bug.cgi?id=982607 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3181) Responsive Skin: select page dialog overflow

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3181?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3181: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=982607 > Responsive Skin: select page dialog overflow > -------------------------------------------- > > Key: GTNPORTAL-3181 > URL: https://issues.jboss.org/browse/GTNPORTAL-3181 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Matt Wringe > > see https://bugzilla.redhat.com/show_bug.cgi?id=982607 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3181) Responsive Skin: select page dialog overflow

by Matt Wringe (JIRA)

Matt Wringe created GTNPORTAL-3181: -------------------------------------- Summary: Responsive Skin: select page dialog overflow Key: GTNPORTAL-3181 URL: https://issues.jboss.org/browse/GTNPORTAL-3181 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe see https://bugzilla.redhat.com/show_bug.cgi?id=982607 -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues July 2013