[gatein-issues] [JBoss JIRA] (GTNPORTAL-1284) Optimize SiteMap portlet by setting a filter on the node tree instead of using PageNavigationUtils.filter

[Boleslaw Dawidowicz (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boleslaw Dawidowicz closed GTNPORTAL-1284.
------------------------------------------

    Resolution: Out of Date


Should be verified in gatein master and reopened if still valid
                
> Optimize SiteMap portlet by setting a filter on the node tree instead of using PageNavigationUtils.filter
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-1284
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-1284
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Minh Hoang TO
>            Assignee: Minh Hoang TO
>              Labels: sprint_35
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
>   In current code of SiteMap portlet, whenever there is a call to reload the tree (on expand/collapse the node), the filter method in PageNavigationsUtils is implicitely invoked. That results in two drawbacks:
> 1. A traverse over navigation trees is required, whereas on rendering , tree traversing is mandatory ( see the UISitemap.gtmpl )
> 2. Multiple data cloning
>  It is better to define a filter in the UISitemap 's tree object and remove the invocation to PageNavigationUtils.filter ( analogous ideas could be found in UIFilterableTree, see GTNPORTAL-1139)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira