>From: "Bharath Belagodu" <[EMAIL PROTECTED]> > >In trying to get panelNavigation2 as a menu option, Im facing this issue of >not able to retain the >components active/selected view when opening a link from the menu onto a new >page. Im using >facelets, tomahawk 1.1.3 and myfaces. > >If the menu looks like, >Menu 1 > First link > Second link >Menu 2 > Third link > Fourth link > >If I click on any of the links above and the menu is displayed on the same >page, >the active/selected item First Link stays. If I right click on the browser >on >Second Link and chose Open link in new window, then the information/action >associated with the Second Link executes, the page is displayed but the menu >is collapsed and the menu state isnt retained. > >Im also trying to bind the panelNavigation2 component to a >HtmlPanelNavigationMenu >in my backing bean but it doesnt seem to work. Ill investigate further but >wanted >to send this email out to the group, just in case someone has already been >through >this path. Thanks.
Your error sounds similar to an issue that Shale Clay uncovered. The panelNavigation2 component needs the pages to have similar structure in order to find the components on the previous page. This was a big issue with Shale Clay at one time because it was forcing a naming container. A naming container adds to the component names so that they are unique within a html form. We have since removed this constraint (http://issues.apache.org/struts/browse/SHALE-316) Well, I'm sure that this is all too interesting since it is not about Facelets :-) but, you might check to make sure that your pages structure is the same (meaning panelNavigation2, form, and subview id's). I proposed that the component should try harder to find itself on the previous page with this patch (https://issues.apache.org/jira/browse/TOMAHAWK-755). For goodness sake, I even included a test case :-0. Gary
