April 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Commented: (GTNPORTAL-1852) Checkbox selection is lost with paginator when add gadget or portlet in categories

by kien nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1852?page=com.atlassian.jira.pl... ] kien nguyen commented on GTNPORTAL-1852: ---------------------------------------- Duplicated with GTNPORTAL-1564 > Checkbox selection is lost with paginator when add gadget or portlet in categories > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-1852 > URL: https://issues.jboss.org/browse/GTNPORTAL-1852 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Affects Versions: 3.1.0-GA > Reporter: Michal Vanco > Labels: portal-s52 > Fix For: 3.2.0-GA > > > Condition: you must have more than 5 categories created > Scenario: > - go to App.registry > - click Gadgets > - add new remote gadget (any) > - click Add gadget to category > - select some category from first page, select second page, select first page again -> selection is lost > Same behavior is in Portlets tab. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (GTNPORTAL-1852) Checkbox selection is lost with paginator when add gadget or portlet in categories

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1852?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-1852: ---------------------------------- Labels: portal-s52 (was: ) > Checkbox selection is lost with paginator when add gadget or portlet in categories > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-1852 > URL: https://issues.jboss.org/browse/GTNPORTAL-1852 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Affects Versions: 3.1.0-GA > Reporter: Michal Vanco > Labels: portal-s52 > Fix For: 3.2.0-GA > > > Condition: you must have more than 5 categories created > Scenario: > - go to App.registry > - click Gadgets > - add new remote gadget (any) > - click Add gadget to category > - select some category from first page, select second page, select first page again -> selection is lost > Same behavior is in Portlets tab. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (GTNPORTAL-1855) The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1855?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-1855: ---------------------------------- Labels: backlogs portal-s52 (was: backlogs) > The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal) > ----------------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-1855 > URL: https://issues.jboss.org/browse/GTNPORTAL-1855 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Common integration > Reporter: Martin Weiler > Labels: backlogs, portal-s52 > Fix For: 3.2.0-GA > > > The changes applied to 02portal.war/WEB-INF/web.xml as a result of the fix for JBEPP-486 also need to be applied to the web.xml files contained in the eppsp demo portal and sample portal. The filter mapping element for the GenericFilter has to be the last one in the list: >  > <filter-mapping> > <filter-name>GenericFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> >  >  >  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (GTNMAVEN-22) Update SLF4J to 1.5.8 for Tomcat.js

by Julien Viet (JIRA)

Update SLF4J to 1.5.8 for Tomcat.js ----------------------------------- Key: GTNMAVEN-22 URL: https://issues.jboss.org/browse/GTNMAVEN-22 Project: GateIn Maven Issue Type: Task Reporter: Julien Viet Assignee: Julien Viet Fix For: packager-1.0.0-CR04 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNMAVEN-21) Update JBoss EAR packaging for JCR 1.14.0-CR1 dependencies

by Julien Viet (JIRA)

Update JBoss EAR packaging for JCR 1.14.0-CR1 dependencies ---------------------------------------------------------- Key: GTNMAVEN-21 URL: https://issues.jboss.org/browse/GTNMAVEN-21 Project: GateIn Maven Issue Type: Task Reporter: Julien Viet Fix For: packager-1.0.0-CR03 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1865) Replace google collection by google guava

by Julien Viet (JIRA)

Replace google collection by google guava ----------------------------------------- Key: GTNPORTAL-1865 URL: https://issues.jboss.org/browse/GTNPORTAL-1865 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Google Guava is an evolution of Google Collection. The existing opensocial codebase relies on Google Collection and can use therefore Google Guava as there is a compatibility. Note that the 2.0 version of opensocial implementation relies on Google Guava. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNPC-58) Improve PortletContext creation

by Chris Laprun (JIRA)

Improve PortletContext creation ------------------------------- Key: GTNPC-58 URL: https://issues.jboss.org/browse/GTNPC-58 Project: GateIn Portlet Container Issue Type: Feature Request Components: API, Documentation Affects Versions: 2.2.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.3.0-Beta02 In particular, it should encapsulate special values and format a lot better than it currently does. Add better validation of input. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNPC-57) Update

by Thomas Heute (JIRA)

Update ------ Key: GTNPC-57 URL: https://issues.jboss.org/browse/GTNPC-57 Project: GateIn Portlet Container Issue Type: Task Reporter: Thomas Heute -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (GTNWSRP-218) Force use of JBoss EL on AS 6

by Chris Laprun (JIRA)

Force use of JBoss EL on AS 6 ----------------------------- Key: GTNWSRP-218 URL: https://issues.jboss.org/browse/GTNWSRP-218 Project: GateIn WSRP Issue Type: Sub-task Components: Admin GUI Affects Versions: 2.1.0-Beta01 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.1.0-Beta02 The EL evaluation engine seems to have changed between AS 5 and AS 6 and results in improper evaluations of expressions leading to calls being made on objects that are not ready to respond to them. More specifically line 77 in /jsf/consumers/consumer.xhtml: rendered=#{!cons.refreshNeeded and cons.active and cons.producerInfo.registrationRequired} Basically, it doesn't seem like the EL expression: !cons.refreshNeeded and cons.active and cons.producerInfo.registrationRequired is properly interpreted (or at the very least, not interpreted like it was on AS 5). When the exception which causes the portlet to fail is thrown, the state is so that the expression should not be completely evaluated: cons.refreshNeeded is true so !cons.refreshNeeded is false, the evaluation of the expression should stop because the result is already known to be false before looking at the rest of the expression (which is the Java behavior, foo && bar results in bar never being evaluated if foo is false). Moreover, cons.active is also false (even though it should never be evaluated). The exception is thrown because, despite the appropriate guards (the first two expressions !cons.refreshNeeded and cons.active), the EL engine still evaluates the last clause when the state of the underlying objects is not ready for such an evaluation as the root exception clearly states (java.lang.IllegalStateException: Registration status not yet known: call refresh first!). For me, this is a bug in the EL evaluation engine. At the very least, this is a huge change in behavior which should be documented somewhere i.e. the fact that you cannot rely on lazy evaluation of expressions in "and" clauses but this seems to be too big a behavioral change (which would also go against how Java works) for it to be proper behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
18
0 / 0

[JBoss JIRA] Created: (GTNWSRP-220) Update to PC 2.3.0-Beta02 and new, stricter PortletContext

by Chris Laprun (JIRA)

Update to PC 2.3.0-Beta02 and new, stricter PortletContext ---------------------------------------------------------- Key: GTNWSRP-220 URL: https://issues.jboss.org/browse/GTNWSRP-220 Project: GateIn WSRP Issue Type: Task Components: Consumer, Producer Affects Versions: 2.1.0-Beta01 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.1.0-Beta02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues April 2011