Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: Facelets/VDL
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      569
    • Status Whiteboard:
      Hide

      cat1 frame size_small importance_large

      Show
      cat1 frame size_small importance_large

      Description

      The call order of listeners is apparently undefined, and the default behavior of
      the RI is not the desirable one.

      Consider a component with a listener attached to it, as well as two
      setPropertyActionListeners.

      <h:commandButton id="button2" value="<<"
      actionListener="#

      {switchlist.move2to1}

      ">
      <f:setPropertyActionListener value="#

      {listholder1}

      "
      target="#

      {switchlistController.listHolder1}

      "/>
      <f:setPropertyActionListener value="#

      {listholder2}

      "
      target="#

      {switchlistController.listHolder2}

      "/>
      </h:commandButton>

      What order will they be called?

      First move2to1 will be called, then setListHolder1, then setListHolder2.

      Which order should they be called?

      Probably setListholder1, setListholder2, then move2to1. After all, it really
      doesn't make sense to set properties after the main component's listener is
      called.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            driscoll
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: