Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0
    • Component/s: Uncategorized
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      170
    • Status Whiteboard:
      Hide

      EGEasy5

      Show
      EGEasy5

      Description

      We currently allow f:param children for commandLink.
      Does it make sense to also allow f:param children for commandButton,
      given that commandLink/commandButton both perform form submits?

        Issue Links

          Activity

          Hide
          Ryan Lubke added a comment -

          I'm not keen on polluting the client ID with this information.
          It makes it difficult for ajax frameworks to get a reference to
          the command button via ID.

          Additionally, you now have an odd concept. You don't have request parameters
          when using this, so users will be surprised when they call #

          {param.whatever}

          and
          find it is null. You have to check #

          {requestScope}

          instead. It's not consistent.

          I think the current implementation is good enough.

          Those using 1.2 with strict javascript-less pages have already solved
          this issue using f:setPropertyActionListener or some other
          similar solution and won't need to use the f:param with
          commandButton.

          Show
          Ryan Lubke added a comment - I'm not keen on polluting the client ID with this information. It makes it difficult for ajax frameworks to get a reference to the command button via ID. Additionally, you now have an odd concept. You don't have request parameters when using this, so users will be surprised when they call # {param.whatever} and find it is null. You have to check # {requestScope} instead. It's not consistent. I think the current implementation is good enough. Those using 1.2 with strict javascript-less pages have already solved this issue using f:setPropertyActionListener or some other similar solution and won't need to use the f:param with commandButton.
          Hide
          Ed Burns added a comment -

          After consideration with the IMPL team, we've decided to let the existing, JS based approach, stand.

          Show
          Ed Burns added a comment - After consideration with the IMPL team, we've decided to let the existing, JS based approach, stand.
          Hide
          Ed Burns added a comment -

          TCK

          Show
          Ed Burns added a comment - TCK
          Hide
          Ed Burns added a comment -

          Prepare to delete "spec" subcomponent.

          Show
          Ed Burns added a comment - Prepare to delete "spec" subcomponent.
          Hide
          Manfred Riem added a comment -

          Closing resolved issue out

          Show
          Manfred Riem added a comment - Closing resolved issue out

            People

            • Assignee:
              ddonahue
              Reporter:
              rogerk
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: