[ http://issues.apache.org/jira/browse/ADFFACES-274?page=comments#action_12446413 ] Matt Cooper commented on ADFFACES-274: --------------------------------------
The page component has limited value because it hard-codes a specific page layout and consumption of MenuModel nodes. Instead I would prefer to see work done with some sort of reusable page template approach where someone could take an example page template and tweak it specifically to their personal needs. Also, such a solution would ideally at maximum keep one copy of the page template per web application rather than one copy per page so maintenance of the template wouldn't negatively impact the page developer. > MenuModel issues in page component > ---------------------------------- > > Key: ADFFACES-274 > URL: http://issues.apache.org/jira/browse/ADFFACES-274 > Project: MyFaces ADF-Faces > Issue Type: Bug > Components: Build > Environment: JBoss 4.0.4/Windows XP > Reporter: David Sanders > > Global buttons should represent a 'path' from root to leaf in a menu tree. > Under trinidad, the page component treats global buttons as a root of a menu > tree. ADF Faces used a type attribute (type=global) and a menu node without > children to represent global buttons separate from other menu items. > Trinidad does away with the type attribute and makes global buttons the root > of a navigation tree. This does not work, as a global button should > represent a path, not a tree root. One solution would be to have a separate > facet for global buttons. The other workaround is to use panelPage together > with navigationPane/nodeStamp facets (which does not work currently), but > then why have a page component at all? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
