Uploaded image for project: 'MyFaces Core'
  1. MyFaces Core
  2. MYFACES-3960

AjaxBehaviorEvent should be queued before ActionEvent

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.23, 2.1.17, 2.2.7
    • Fix Version/s: 2.0.24, 2.1.18, 2.2.8
    • Component/s: JSR-314, JSR-344
    • Labels:
      None

      Description

      From Bauke Scholtz

      Trigger:
      http://stackoverflow.com/q/28901284

      Code:
      <h:commandLink action="#

      {bean.action}

      ">
      <f:ajax listener="#

      {bean.listener}

      " />
      </h:commandLink>

      Mojarra:
      Listener is first invoked and then action.

      MyFaces:
      Action is first invoked and then listener.

      Who's correct? I couldn't find this in the spec. We need to align out it. As the action is supposed to be definitive (because of the navigation case outcome), I find Mojarra behavior is correct.

      It looks like an exception to the general rule (decode and then decode client behaviors), so we need to decode, decode client behaviors and queue ActionEvent at last.

        Attachments

          Activity

            People

            • Assignee:
              lu4242 Leonardo Uribe
              Reporter:
              lu4242 Leonardo Uribe
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: