ICEfaces
  1. ICEfaces
  2. ICE-3775

Regression: menus do not stay open under certain circumstances

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.7.2
          • Fix Version/s: 1.8RC1, 1.8
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            OC4J 10gR3 / Windows XP, OC4J 10gR3 / SuSE Linux Enterprise 10, Tomcat 6 / Windows XP
            Firefox 2 / Windows XP
            IE6 / Windows XP

            Description

            Under certain circumstances, menus do not stay open. In particular this has been noted where:

            - the menu is driven from a backing bean (i.e. <ice:menuItems value="#{...}"/> is used)
            - an interval renderer is employed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Alistair Young added a comment -

              The attached WAR file demonstrates the problem. Source code can be provided if required.

              Show
              Alistair Young added a comment - The attached WAR file demonstrates the problem. Source code can be provided if required.
              Hide
              Permalink
              Alistair Young added a comment -

              I should have added that this problem did not occur in ICEfaces 1.6.2 or 1.7.0.

              Show
              Alistair Young added a comment - I should have added that this problem did not occur in ICEfaces 1.6.2 or 1.7.0.
              Hide
              Permalink
              Adnan Durrani added a comment -

              Can you please attach the TestBean.java as well?

              Show
              Adnan Durrani added a comment - Can you please attach the TestBean.java as well?
              Hide
              Permalink
              Alistair Young added a comment -

              Happy to oblige - here you go.

              Show
              Alistair Young added a comment - Happy to oblige - here you go.
              Hide
              Permalink
              Adnan Durrani added a comment -

              Seems like MenuItem(s) requires ids inside the bean (e.g.)

              MenuItem item;
              MenuItem subItem;

              item = new MenuItem();
              //set id
              item.setId("one");
              item.setValue("One");

              subItem = new MenuItem();
              //set id
              item.setId("one-1");
              subItem.setValue("One.1");

              Please let us know if it fixes the problem.

              Show
              Adnan Durrani added a comment - Seems like MenuItem(s) requires ids inside the bean (e.g.) MenuItem item; MenuItem subItem; item = new MenuItem(); //set id item.setId("one"); item.setValue("One"); subItem = new MenuItem(); //set id item.setId("one-1"); subItem.setValue("One.1"); Please let us know if it fixes the problem.
              Hide
              Permalink
              Alistair Young added a comment -

              Yes - that did it. And putting the same fix into our real application means that our menus now behave like they did back in v1.7.0.

              Many thanks.

              Show
              Alistair Young added a comment - Yes - that did it. And putting the same fix into our real application means that our menus now behave like they did back in v1.7.0. Many thanks.
              Hide
              Permalink
              Adnan Durrani added a comment -

              This was an application issue, and adding ids to the dynamic menu fixes the problem. This is JSF requirement to pass Ids when creating dynamic components from the bean.

              Alistair Young mentioned in his last post that, his app was fixed by adding the ids to menu components. So I think this case was open by mistakenly.

              Please reopen if it is not the case.

              Show
              Adnan Durrani added a comment - This was an application issue, and adding ids to the dynamic menu fixes the problem. This is JSF requirement to pass Ids when creating dynamic components from the bean. Alistair Young mentioned in his last post that, his app was fixed by adding the ids to menu components. So I think this case was open by mistakenly. Please reopen if it is not the case.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Alistair Young
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: