incubator-adffaces-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias We├čendorf (JIRA) <adffaces-iss...@incubator.apache.org>
Subject [jira] Updated: (ADFFACES-274) MenuModel issues in page component
Date Fri, 16 Mar 2007 08:41:30 GMT

     [ https://issues.apache.org/jira/browse/ADFFACES-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matthias We├čendorf updated ADFFACES-274:
----------------------------------------

    Affects Version/s: 1.0.1-incubating-core-SNAPSHOT

> MenuModel issues in page component
> ----------------------------------
>
>                 Key: ADFFACES-274
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-274
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.0.1-incubating-core-SNAPSHOT
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message