February 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1298) Conflict between Dashboard Tab and site pages url

by Khalil AISSAOUI (JIRA)

Conflict between Dashboard Tab and site pages url ------------------------------------------------- Key: GTNPORTAL-1298 URL: https://jira.jboss.org/browse/GTNPORTAL-1298 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-CR01 Reporter: Khalil AISSAOUI Fix For: 3.1.0-GA To reproduce the problem you have to: * Launch GateIn * Connect as "root" * Click on "Dashboard" * Rename "Tab_0" to "home" ==> Redirected to home page and can't add, delete, modify your dashboard. -- 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

13 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1311) Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively

by Minh Hoang TO (JIRA)

Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively ----------------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-1311 URL: https://jira.jboss.org/browse/GTNPORTAL-1311 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Minh Hoang TO Assignee: Minh Hoang TO In legacy code, both UINavigationPortlet and UISitemapPortlet use UIPortalNavigation to handle the underlying navigations. That was logical in the past as before navigation portlet showed all PageNavigations as UISitemap did. Now, the methods declared in UIPortalNavigaton belongs to two independent groups, one group consists of methods used in sitemap portlet. The other consists of methods used in navigation portlet. On the other hand, using UIPortalNavigation in sitemap portlet requires storing template name in the PortletPreference. Hence, it 's better to split UIPortalNavigation into two classes now -- 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

13 years, 4 months

4
11
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1605) Merging PageNavigations should also merge child PageNodes

by Matt Wringe (JIRA)

Merging PageNavigations should also merge child PageNodes --------------------------------------------------------- Key: GTNPORTAL-1605 URL: https://jira.jboss.org/browse/GTNPORTAL-1605 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe The PageNavigation.merge command only merges in top level PageNodes, if a PageNode with the same name already exists, it will overwrite the previous node with a new one. This prevents being able to add a new page node to a subnode which already exists. For example, the administration node by default contains the app-registry and page-management PageNodes. I cannot use the extension mechanism to add an extra PageNode here, since the PageNavigation.merge will delete the current administration node and overwrite it with the one I specify in the extension. In this situation I am stuck adding it to another top level location, which is not ideal. What should happen is that the child PageNodes get merged together, so that I can add extra nodes anywhere in the PageNode tree. This will however change the behaviour of how extensions work. What this means is that you can no longer overwrite or remove PageNodes using the extension mechanism. -- 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

13 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1737) Can't loogin to portal when input ULR with sepecial case

by Hang Nguyen (JIRA)

Can't loogin to portal when input ULR with sepecial case -------------------------------------------------------- Key: GTNPORTAL-1737 URL: https://issues.jboss.org/browse/GTNPORTAL-1737 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hang Nguyen - Input URL on adress barby: http://localhost:8080/portal/private/classic/groupnavigation?portal:compo... - Input user name and pass - Click Sign in => can't login to portal and Return to public mode Expected output: After input user and pass and click Sign In => Login in successfully -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1740) GateIn 3.1.0-GA won't build with Maven 3

by Benito Bertoli (JIRA)

GateIn 3.1.0-GA won't build with Maven 3 ---------------------------------------- Key: GTNPORTAL-1740 URL: https://issues.jboss.org/browse/GTNPORTAL-1740 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Environment: OS: Win7-x64 Home Premium java jdk6 maven 3.0.1 Reporter: Benito Bertoli I downloaded GateIn 3.1.0 src and tried to build it using maven. I used "mvn clean install" and got the following error: [INFO] Scanning for projects... [ERROR] The build could not read 6 projects -> [Help 1] [ERROR] [ERROR] The project org.exoplatform.portal:exo.portal.sample.extension.root:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\extension\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 24, column 11 -> [Help 2] [ERROR] [ERROR] The project org.exoplatform.portal:exo.portal.sample.portal.root:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\portal\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 24, column 11 -> [Help 2] [ERROR] [ERROR] The project org.gatein.portal.examples.portlets:parent:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\portlets\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 12 -> [Help 2] [ERROR] [ERROR] The project org.gatein.portal.examples.skins:parent:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\examples\skins\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 12 -> [Help 2] [ERROR] [ERROR] The project org.exoplatform.portal:exo.portal.starter.war:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\starter\war\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 23, column 11 -> [Help 2] [ERROR] [ERROR] The project org.exoplatform.portal:starter-gatein:3.1.0-GA (C:\Users\BiNO\workspace\GateIn-3.1.0-GA\starter\ear\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.exoplatform.portal:exo.portal.parent:pom:3.1.0-GA in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 23, column 11 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
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

13 years, 4 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

13 years, 4 months

4
11
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

13 years, 4 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

13 years, 4 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

13 years, 4 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues February 2011