Details

    • Type: Improvement Improvement
    • Status: Reopened
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.1, 1.2, 2.0, 2.1
    • Fix Version/s: None
    • Component/s: Facelets/VDL
    • Labels:
      None
    • Status Whiteboard:
      Hide

      size_large impotance_large

      Show
      size_large impotance_large

      Description

      >>>>> On Sat, 23 Apr 2011 18:41:42 +0000, Jason Bonifay said:

      JB> 1) the classic "cascading drop down problem" - this is a scenario
      JB> where the first dropdown is dynamically populated with values and
      JB> the selection available in the second dropdown is dependent on the
      JB> value selected in the first dropdown (e.g.: select a country then
      JB> the list of cities are dynamically populated). Important to note
      JB> here - if dropdown #1 has static values this problem obviously
      JB> trivial, the challenge arises from a dynamically defined list being
      JB> dependent on the selected value from a parent list the is also
      JB> dynamically defined. ASP.NET solves this (and other problems) by
      JB> defining several "page lifecycle functions" akin to JSF but let's
      JB> you easily override functions in the backing classes (i.e.:
      JB> "page_init", "page_load" etc) to programmatically control where to
      JB> populate each dropdown. Remember - You can't paint the values in
      JB> dropdown #2 until you can retrieve the selected index from dropdown
      JB> #1 - but you can't retrieve the selected index until you first fill
      JB> the options so the framework can then bind the selected index.

        Activity

        Hide
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Ed Burns added a comment -

        I don't think we made the var attribute optional after all.

        Show
        Ed Burns added a comment - I don't think we made the var attribute optional after all.
        Hide
        lamine_ba added a comment -

        You are right Jakob and I vote for "item". Don't worry, nothing has been done yet. It was just an idea we were testing.

        Show
        lamine_ba added a comment - You are right Jakob and I vote for "item". Don't worry, nothing has been done yet. It was just an idea we were testing.
        Hide
        Jakob Korherr added a comment -

        Hi Lamine,

        Thanks a lot for the clarification. I did not know that!

        Nevertheless, I prefer "item" over "it". It really is a lot more significant in this case, because most attributes of <f:selectItems> which will use this implicit var are starting with the term "item" --> "itemLabel", "itemValue".

        So it would be very great, if we could change that!

        Show
        Jakob Korherr added a comment - Hi Lamine, Thanks a lot for the clarification. I did not know that! Nevertheless, I prefer "item" over "it". It really is a lot more significant in this case, because most attributes of <f:selectItems> which will use this implicit var are starting with the term "item" --> "itemLabel", "itemValue". So it would be very great, if we could change that!

          People

          • Assignee:
            Unassigned
            Reporter:
            Ed Burns
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: