[gatein-issues] [JBoss JIRA] Created: (GTNPORTAL-2140) Hardcoded Scope.GRANDCHILDREN in UINavigationNodeSelector

Hardcoded Scope.GRANDCHILDREN in UINavigationNodeSelector --------------------------------------------------------- Key: GTNPORTAL-2140 URL: https://issues.jboss.org/browse/GTNPORTAL-2140 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Performance Affects Versions: 3.2.0-M01 Reporter: Marek Posolda Fix For: 3.2.0-M02 I am testing with many pages/nodes and I have portal with 27 navigation nodes at navigation bar and each have additional 27 navigation nodes. So I have 27 + 27^2 = 756 navigation nodes. I tried to change default scope value 2 to value 1 because loading of 756 is very expensive and took more than 100 seconds. So I changed preference "level" for UINavigationPortlet, SiteMapPortlet, UIUserToolbarSitePortlet, UIUserToolbarGroupPortlet, UIUserToolbarDashboardPortlet. This helped to avoid expensive load of all nodes when working with portal. However there is still one place in class UINavigationNodeSelector, where is hardcoded scope to value 2 and when I am trying to edit navigation of my portal, it's loading 120 seconds. Is it possible to make it configurable so that users can change it to 1 or other value according to their preference? Steps to reproduce: 1) Add portal site with 27 + 27^2 navigation nodes and pages. I am attaching my XML descriptors for this site named "myportal2". 2) Change "level" preference in web.war/WEB-INF/portlet.xml and exoadmin.war/WEB-INF/portlet.xml for UINavigationPortlet, SiteMapPortlet, UIUserToolbarSitePortlet, UIUserToolbarGroupPortlet, UIUserToolbarDashboardPortlet 3) Start portal against emtpy database 4) Login as root 5) http://localhost:8080/portal/classic/portalnavigation and click to "Edit navigation" of portal "myportal2" Now I need to wait around 120 seconds because UINavigationNodeSelector.initTreeData() needs to load all 756 nodes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira