incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Cooper" <>
Subject Re: page component and global buttons
Date Fri, 27 Oct 2006 22:13:49 GMT

Please correct me if I'm wrong, but I believe (regardless of type) that
Trinidad treats top level of the MenuModel as global nodes and the next
level down is for the tabs.  Whereas the ADF Faces 10.1.3 model treated the
global nodes and tabs as items from the same level of the MenuModel
(distinguished by that type setting as you mentioned).


On 10/27/06, d sanders <> wrote:
> Hello,
> ADF Faces used the 'type' attribute on the nodeStamp
> facet's commandMenuItem to determine whether or not
> the nodeStamp represented a global button when
> rendering a page component.  From the oracle docs:
> "
> Instead of a menuGlobal facet, the page component
> supports global menu buttons from the menu model only.
> Items to be rendered as global buttons are added to
> the menu model as peers of the menu tab items, and in
> the JSF page the type attribute of the associated menu
> item component should return  global. Suppose you have
> a menu hierarchy where a1, a2 are top-level nodes with
> various children subnodes, and a3, a4 are standalone
> nodes with no children subnodes (as shown in the
> illustration below)."
> It looks like trinidad gets rid of the type attribute
> (and renames the commandMenuItem to
> commandNavigationItem).  So there is no way to tell
> the renderer that you don't want the item to be a
> global button.  Am I missing something?
> Thanks
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message