incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d sanders <dsanders1...@yahoo.com>
Subject page component and global buttons
Date Fri, 27 Oct 2006 18:11:46 GMT
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)."

http://www.oracle.com/webapps/online-help/jdeveloper/10.1.3/state/content/navId.4/navSetId._/vtAnchor.global/vtTopicFile.jsf_apps%7Cadfcreate%7Caf_alay_pagecomponent%7Ehtml/

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 
http://mail.yahoo.com 

Mime
View raw message