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) Affects Versions: 3.1.0-GA Reporter: Minh Hoang TO Assignee: Vu Viet Phuong Fix For: 3.2.0-GA Original Estimate: 6 hours Remaining Estimate: 6 hours 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

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) Affects Versions: 3.1.0-GA Reporter: Minh Hoang TO Assignee: Vu Viet Phuong Fix For: 3.2.0-GA Original Estimate: 6 hours Remaining Estimate: 6 hours 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

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) Affects Versions: 3.1.0-GA Reporter: Minh Hoang TO Assignee: Vu Viet Phuong Fix For: 3.2.0-GA Attachments: 2010-09-15-GTNPORTAL-1311.patch Original Estimate: 6 hours Remaining Estimate: 6 hours 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

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) Affects Versions: 3.1.0-GA Reporter: Minh Hoang TO Assignee: Vu Viet Phuong Labels: navcontroller, portal-s43, sprint_38, sprint_39, worked Fix For: 3.2.0-GA Attachments: 2010-09-15-GTNPORTAL-1311.patch Original Estimate: 4 hours Remaining Estimate: 4 hours 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

Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively ----------------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-1311 URL: https://issues.jboss.org/browse/GTNPORTAL-1311 Project: GateIn Portal Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 3.1.0-GA Reporter: Minh Hoang TO Assignee: Vu Viet Phuong Labels: navcontroller, portal-s43, sprint_38, sprint_39, worked Fix For: 3.2.0-M02 Attachments: 2010-09-15-GTNPORTAL-1311.patch Original Estimate: 4 hours Remaining Estimate: 4 hours 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