ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-203

Slider Example error/warning messages.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-2.0.0.Alpha1
          • Fix Version/s: EE-2.0.0.Beta1
          • Component/s: Facelet Components
          • Labels:
            None
          • Environment:
            JSF 2.1
          • Workaround Description:
            Hide
            When deploying the application, make sure the the following context param is set, which will stop the warning in Error 1 from displaying.

                <context-param>
                    <param-name>javax.faces.PROJECT_STAGE</param-name>
                    <param-value>Production</param-value>
                </context-param>
            Show
            When deploying the application, make sure the the following context param is set, which will stop the warning in Error 1 from displaying.     <context-param>         <param-name>javax.faces.PROJECT_STAGE</param-name>         <param-value>Production</param-value>     </context-param>

            Description

            The slider example like other displays the following message in the <h:messages /> tag:

            Error 1:
            The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within.

            Error 2:
            The example also shows the following error which is specific to the example:
            Warning: This page calls for XML namespace declared with prefix html but no taglibrary exists for that namespace.
            Warning: This page calls for XML namespace declared with prefix html but no taglibrary exists for that namespace.
            Warning: This page calls for XML namespace declared with prefix html but no taglibrary exists for that namespace.
            Warning: This page calls for XML namespace declared with prefix html but no taglibrary exists for that namespace

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Patrick Corless added a comment -

              Brad pointed out that xmlns="http://www.w3.org/1999/xhtml" is likely missing in the demo or component xhtml code.

              Show
              Patrick Corless added a comment - Brad pointed out that xmlns="http://www.w3.org/1999/xhtml" is likely missing in the demo or component xhtml code.
              Hide
              Permalink
              Carlo Guglielmin added a comment -

              r25997 - The slider component was missing the 'xmlns' namespace, but used an html tag, so an error was thrown. This check-in adds the proper namespace. This fixes the second warning we were seeing.

              Show
              Carlo Guglielmin added a comment - r25997 - The slider component was missing the 'xmlns' namespace, but used an html tag, so an error was thrown. This check-in adds the proper namespace. This fixes the second warning we were seeing.
              Hide
              Permalink
              Carlo Guglielmin added a comment -

              The warning:
              "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within h:form"
              looks to be a bug in JSF, as talked about at the following resources:

              http://java.net/jira/browse/JAVASERVERFACES-1922
              https://issues.jboss.org/browse/RF-9925
              http://stackoverflow.com/questions/4089076/glassfish-3-1-b-25-weird-form-error-the-form-component-needs-to-have-a-uiform

              As a note switching the web.xml context param "javax.faces.PROJECT_STAGE" from "Development" to "Production" makes the warning disappear.

              Show
              Carlo Guglielmin added a comment - The warning: "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within h:form" looks to be a bug in JSF, as talked about at the following resources: http://java.net/jira/browse/JAVASERVERFACES-1922 https://issues.jboss.org/browse/RF-9925 http://stackoverflow.com/questions/4089076/glassfish-3-1-b-25-weird-form-error-the-form-component-needs-to-have-a-uiform As a note switching the web.xml context param "javax.faces.PROJECT_STAGE" from "Development" to "Production" makes the warning disappear.
              Hide
              Permalink
              Patrick Corless added a comment -

              When deploying the application, make sure the the following context param is set

              <context-param>
              <param-name>javax.faces.PROJECT_STAGE</param-name>
              <param-value>Production</param-value>
              </context-param>

              Show
              Patrick Corless added a comment - When deploying the application, make sure the the following context param is set <context-param> <param-name>javax.faces.PROJECT_STAGE</param-name> <param-value>Production</param-value> </context-param>
              Hide
              Permalink
              Patrick Corless added a comment -

              Closing, the work around is good enough for now until the JSF issue is fixed.

              Show
              Patrick Corless added a comment - Closing, the work around is good enough for now until the JSF issue is fixed.

                People

                • Assignee:
                  Carlo Guglielmin
                  Reporter:
                  Patrick Corless
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: