ICEfaces
  1. ICEfaces
  2. ICE-4490

compat component-showcase navigation

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Alpha1
          • Fix Version/s: 2.0-Alpha1, 2.0.0
          • Component/s: Sample Apps
          • Labels:
            None
          • Environment:
            ICEfaces 2.0

            Description

            Navigation required two clicks to succeed in compat/samples/component-showcase.

            This is due to the fact that the detail panels are displayed via <ui:include> which must be evaluated to create the component tree prior to input values being decoded. This caused the selected detail view to lag behind by one step.

            The solution is to use the <f:param> directly from the request map in the NavigationBean getter:

                public String getSelectedIncludePath() {
                    //check for a currently selected path to be ready for ui:include
                    FacesContext context = FacesContext.getCurrentInstance();
                    Map map = context.getExternalContext().getRequestParameterMap();
                    String requestedPath = (String) map.get("includePath");
                    if (null != requestedPath) {
                        selectedIncludePath = requestedPath;
                    }
                    return selectedIncludePath;
                }

              Activity

              Hide
              Permalink
              Ted Goddard added a comment -

              Occasionally the parameter would be "" and not null – perhaps it was created as a hidden field in the browser and is now being serialized with no value. The following change to NavigationBean addresses this:

              • if (null != requestedPath) {
                + if ((null != requestedPath) && (requestedPath.length() > 0)) {
              Show
              Ted Goddard added a comment - Occasionally the parameter would be "" and not null – perhaps it was created as a hidden field in the browser and is now being serialized with no value. The following change to NavigationBean addresses this: if (null != requestedPath) { + if ((null != requestedPath) && (requestedPath.length() > 0)) {

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Ted Goddard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: