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

          Activity

          Deryk Sinotte created issue -
          Icefaces Administrator made changes -
          Field Original Value New Value
          issue.field.bugzillaimportkey 332 11598
          made changes -
          Link This issue depends on ICE-452 [ ICE-452 ]
          Ken Fyten made changes -
          Affects Version/s 1.5 [ 10027 ]
          Affects Version/s Alpha [ 10022 ]
          Ken Fyten made changes -
          Priority Major [ 3 ] Minor [ 4 ]
          Ken Fyten made changes -
          Assignee Mircea Toma [ mircea.toma ]
          Ken Fyten made changes -
          Link This issue blocks ICE-1035 [ ICE-1035 ]
          Ken Fyten made changes -
          Salesforce Case []
          Ken Fyten made changes -
          Salesforce Case []
          Ken Fyten made changes -
          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?

          ]
          Ken Fyten made changes -
          Assignee Ken Fyten [ ken.fyten ]
          Ken Fyten made changes -
          Salesforce Case []
          Fix Version/s 2.0-Beta [ 10231 ]
          Fix Version/s 2.0-Alpha3 [ 10032 ]
          Ken Fyten made changes -
          Fix Version/s 2.0-Beta2 [ 10242 ]
          Fix Version/s 2.0-Beta1 [ 10231 ]
          Ken Fyten made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Invalid [ 6 ]
          Assignee Ken Fyten [ ken.fyten ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved: