Hi Mike, You can go ahead and do that if you think that it is the best solution, but I just wanted to point out that NavigationMenuItem is a single class, not a component. And it is only getters/setters.
Regards, Sharath --- Mike Kienenberger <[EMAIL PROTECTED]> wrote: > On 4/27/06, sharath reddy <[EMAIL PROTECTED]> > wrote: > > PanelNavigation2 and jsCookMenu have the ability > to > > pull their menu options off a backing bean. They > both > > use NavigationMenuItem for that. Each instance of > > NavigationMenuItem represents a node in the menu, > and > > contains information like action to be executed, > icon > > to be displayed, etc. It also contains an array > list > > of NavigationMenuItems so as to support > multi-level > > menus. > > > > The upcoming OutlookMenu component will also use > > NavigationMenuItem objects for dynamic > configuration > > to maintain consistency. > > > > I dont think PanelNavigation uses > NavigationMenuItem. > > Thanks! > > I'm going to go ahead and create a new > NavigationMenuItem component in > the Tomahawk issue tracker. It sounds like it > should have one of its > own. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
