ICEfaces
  1. ICEfaces
  2. ICE-329

Components must be contained within a form

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Minor Minor
          • Resolution: Invalid
          • Affects Version/s: 1.5
          • Fix Version/s: 2.0-Beta2
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Operating System: All
            Platform: All

            Description

            If you have a page with components bound to backing beans and you want to update
            those via server-side render calls, it seems that the components MUST be
            contained with a form for the render calls to actually facilitate an update in
            the browser. Without a containing form, the page does not seem to update.

            I'm not sure what the inherent issues might be in implementing or changing this
            behaviour but it probably should at least be documented somewhere once we
            understand the exact parameters of the behaviour.

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-1035 panelTabSet must be in a Form

              • Minor - Minor loss of function, or other problem where easy workaround is present.
              • Closed
              depends on

              Bug - A problem which impairs or prevents the functions of the product. ICE-452 Remove the need for enclosing forms.

              • Minor - Minor loss of function, or other problem where easy workaround is present.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                5 older comments
                Hide
                Permalink
                Steve Maryka added a comment -

                Add to known issues.

                Show
                Steve Maryka added a comment - Add to known issues.
                Hide
                Permalink
                Ken Fyten added a comment -

                Assign to Mircea, target v1.1. This seems like a duplicate of 454 to me.

                Show
                Ken Fyten added a comment - Assign to Mircea, target v1.1. This seems like a duplicate of 454 to me.
                Hide
                Permalink
                Ken Fyten added a comment -

                Lower priority, out of scope for v1.1. release.

                Show
                Ken Fyten added a comment - Lower priority, out of scope for v1.1. release.
                Hide
                Permalink
                Ken Fyten added a comment -

                JSF Standard Behavior:

                1. All JavaServer Faces pages are represented by a tree of components, called a view. The view tag represents the root of the view.
                2. All JavaServer Faces component tags must be inside of a view tag, which is defined in the core tag library.
                3. The form tag represents an input form component, which allows the user to input some data and submit it to the server, usually by clicking a button. 4. All UI component tags that represent editable components (such as text fields and menus) must be nested inside the form tag.

                So, 1st question, do ICEfaces 2.0 components conform to the above spec., or do all ICEfaces comps. need to be in a form regardless?
                2nd question is what happens with none-editable components such as tabSet, that do have a selectedIndex value?

                Show
                Ken Fyten added a comment - JSF Standard Behavior: 1. All JavaServer Faces pages are represented by a tree of components, called a view. The view tag represents the root of the view. 2. All JavaServer Faces component tags must be inside of a view tag, which is defined in the core tag library. 3. The form tag represents an input form component, which allows the user to input some data and submit it to the server, usually by clicking a button. 4. All UI component tags that represent editable components (such as text fields and menus) must be nested inside the form tag. So, 1st question, do ICEfaces 2.0 components conform to the above spec., or do all ICEfaces comps. need to be in a form regardless? 2nd question is what happens with none-editable components such as tabSet, that do have a selectedIndex value?
                Hide
                Permalink
                Ken Fyten added a comment -

                The limitations outlined above (input and action components must be included in a form) are recognized as standard within JSF. As such, ICEfaces complies with this standard.

                Show
                Ken Fyten added a comment - The limitations outlined above (input and action components must be included in a form) are recognized as standard within JSF. As such, ICEfaces complies with this standard.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Deryk Sinotte
                  • Votes:
                    1 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: