ICEfaces
  1. ICEfaces
  2. ICE-6701

Core Auction sample erroneously reports "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Trivial Trivial
          • Resolution: Won't Fix
          • Affects Version/s: 2.0.1
          • Fix Version/s: 3.0
          • Component/s: Sample Apps
          • Labels:
            None
          • Environment:
            ICEfaces 2.0.1, samples/core/auction sample.
          • Workaround Exists:
            Yes
          • Workaround Description:
            Setting the PROJECT_STAGE to "Production" will remove these warnings.

            Description

            When running the Auction sample application with ICEfaces 2.0.1 in "Development" PROJECT_STAGE, the following JSF warning is present on the bottom left section of the page:

            "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"

            This seems likely to be a Mojarra JSF bug, since it started when JSF 2.1.0 and auction application itself uses all "h:" components and definitely has an "h:form" on the page.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Tony D added a comment -

              Bug exists in 2.02 for custom web application ie not one of the sample apps
              Workaround successful.
              Ugly to develop with though!

              Show
              Tony D added a comment - Bug exists in 2.02 for custom web application ie not one of the sample apps Workaround successful. Ugly to develop with though!
              Hide
              Permalink
              Ken Fyten added a comment -

              Closing this issue as "Won't Fix" as it is caused by a bug in Mojarra JSF runtimes.

              See http://java.net/jira/browse/JAVASERVERFACES-1922 for details (apparently fixed in the upcoming Mojarra JSF 2.2 release).

              Show
              Ken Fyten added a comment - Closing this issue as "Won't Fix" as it is caused by a bug in Mojarra JSF runtimes. See http://java.net/jira/browse/JAVASERVERFACES-1922 for details (apparently fixed in the upcoming Mojarra JSF 2.2 release).

                People

                • Assignee:
                  Cruz Miraback
                  Reporter:
                  Ken Fyten
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: