April 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1872) Sprint 52 activities

by kien nguyen (JIRA)

Sprint 52 activities -------------------- Key: GTNPORTAL-1872 URL: https://issues.jboss.org/browse/GTNPORTAL-1872 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: kien nguyen -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1609) Can't do any action after open 3 Popup Windown

by Hang Nguyen (JIRA)

Can't do any action after open 3 Popup Windown ---------------------------------------------- Key: GTNPORTAL-1609 URL: https://jira.jboss.org/browse/GTNPORTAL-1609 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hang Nguyen - Go to group Navigation - Click Edit navigation - Add new node -> Add new node appear - Choose Page Selector - Click Search and Select page - Input page name which does not exits in list - Click Search => show message -> OK - Close all popup window => Can't do any action after open 3 Popup Windown -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1720) Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler

by Minh Hoang TO (JIRA)

Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler --------------------------------------------------------------------------------- Key: GTNPORTAL-1720 URL: https://jira.jboss.org/browse/GTNPORTAL-1720 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Minh Hoang TO {code:java} /** * Sets a boolean value to force whether portal will be fully rendered * and it is only effective to an Ajax request.<p/> * * if the value is set to <code>true</code>, it means :<br/> * * 1) Only portal ui components are rendered <br/> * 2) Portlets will be fully rendered if are inner of the portal ui components being updated * * @param forceFullUpdate */ final public void setFullRender(boolean forceFullUpdate) { this.forceFullUpdate = forceFullUpdate; } {code} As mentioned in the Javadoc, while AJAX update is used, the forceFullUpdate decide whether only component of portal (ie: The components outside portlet window UIPortlet such as UIMaskWorkspace, UIWorkingWorkspace,...) The name of method is very confusing. If we wish to update only components of portal, we have to call setFullRender(true) (I'm sure that most developers think of setFullRender(false) ) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1866) Issue with picketlink cache - cached items are never evicted

by Marek Posolda (JIRA)

Issue with picketlink cache - cached items are never evicted ------------------------------------------------------------ Key: GTNPORTAL-1866 URL: https://issues.jboss.org/browse/GTNPORTAL-1866 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: EPP 5.1.0.GA, Picketlink version is 1.1.7.GA Reporter: Marek Posolda Assignee: Boleslaw Dawidowicz I think there is issue related to expiration of JBoss cache entries, which are used for picketlink cache. Right now, JBoss cache in server/default/deploy/gatein.ear/02portal.war/WEB-INF/organization/picketlink-idm/jboss-cache.xml and jboss-cache-cluster.xml is configured to use Expiration algorithm: <eviction wakeUpInterval="5000"> <default algorithmClass="org.jboss.cache.eviction.ExpirationAlgorithm" eventQueueSize="1000000"> <property name="maxNodes" value="100000" /> <property name="timeToLive" value="120000" /> <property name="warnNoExpirationKey" value="false" /> </default> </eviction> Problem is that ExpirationAlgorithm requires support in Java code for eviction, which is mentioned in http://docs.jboss.org/jbosscache/3.1.0.CR1/userguide_en/html/eviction_pol... . There is need to call something like: // sets the expiry time for a node cache.getRoot().addChild(fqn1).put(ExpirationConfiguration.EXPIRATION_KEY, future); otherwise node is never evicted periodically. And I am seeing that this is not called in Picketlink code and GateIn+Picketlink integration code. And I am seeing in JMX that nodes are never evicted automatically after some time. Fact is that entries are cleared from cache only by trigger of some events (For example after update of some user are entries for this user evicted from cache). Last week I was working on application for adding users into GateIn IDM database only with plain SQL. And when I create users, I am not seeing them in organization management portlet because query for get all users is never evicted from cache. I need to restart my GateIn portal or trigger JMX eviction of picketlink cache (Operation "invalidateAll" on MBean exo:name=plidmcache,portal="portal",service=PicketLinkIDMCacheService . -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1860) gadget portlet wrapper doesn't support user preferences

by Nick Scavelli (JIRA)

gadget portlet wrapper doesn't support user preferences ------------------------------------------------------- Key: GTNPORTAL-1860 URL: https://issues.jboss.org/browse/GTNPORTAL-1860 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Nick Scavelli User preferences are ignored in gadget portlet wrapper. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1831) Update location of SSO packaging in reference guide

by Marek Posolda (JIRA)

Update location of SSO packaging in reference guide --------------------------------------------------- Key: GTNPORTAL-1831 URL: https://issues.jboss.org/browse/GTNPORTAL-1831 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.1.0-GA Environment: Reference guide http://docs.jboss.com/gatein/portal/3.1.0-FINAL/reference-guide/en-US/htm... Reporter: Marek Posolda Assignee: Luc Texier Fix For: 3.2.0-GA In SSO chapter in 6.6.1.1 paragraph is old location for SSO packaging http://repository.jboss.org/maven2/org/gatein/sso/sso-packaging . I think it needs to be updated to link https://repository.jboss.org/nexus/content/groups/public/org/gatein/sso/s... . Newest SSO-packaging version 1.0.1-GA can be found only under new repository location but not under old location. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1824) We should implement all Unsupported method in UserHandler interface

by Khoi Nguyen (JIRA)

We should implement all Unsupported method in UserHandler interface ------------------------------------------------------------------- Key: GTNPORTAL-1824 URL: https://issues.jboss.org/browse/GTNPORTAL-1824 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Khoi Nguyen Currently, some methods in UserHandler have been deprecated and suggested to use other method such as * getUserPageList -> findAllUsers * findUsers -> findUsersByQuery * findUsersByGroup -> findUsersByGroupId Unfortunately, these methods haven't been implemented yet and throw UnsupportedOperationException, there're very confusing for developer who want to use this API, so we must implement them as soon as possible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1794) Remove WebOS checking from UIPageBrowser.DeleteActionListener

by Vu Viet Phuong (JIRA)

Remove WebOS checking from UIPageBrowser.DeleteActionListener ------------------------------------------------------------- Key: GTNPORTAL-1794 URL: https://issues.jboss.org/browse/GTNPORTAL-1794 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong Priority: Minor There are some code that relate to WebOS. It should be removed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1793) Should not allow to delete pages of other users (page that have OwnerType : user)

by Vu Viet Phuong (JIRA)

Should not allow to delete pages of other users (page that have OwnerType : user) --------------------------------------------------------------------------------- Key: GTNPORTAL-1793 URL: https://issues.jboss.org/browse/GTNPORTAL-1793 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong UIPageBrowser is not designed to delete page of other users. For example : login as root, go to PageManagement, delete user::demo::tab_0 But UIPageBrowser is only to be designed to delete pages of current user, not other user. To delete all user pages. we can delete user account -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1787) Remove WebOS related ResourceBundle keys

by Vu Viet Phuong (JIRA)

Remove WebOS related ResourceBundle keys ---------------------------------------- Key: GTNPORTAL-1787 URL: https://issues.jboss.org/browse/GTNPORTAL-1787 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong Priority: Minor There are some keys that only WebOS project use, we should move it to WebOS webui_*.properties GroovyPortlet_*.properties -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues April 2011