MyFaces Core
  1. MyFaces Core
  2. MYFACES-3337

param defined with f:param inside h:button or h:link has precedence over the same param defined in a faces-config navigation rule

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.10, 2.1.4
    • Component/s: JSR-314
    • Labels:
      None

      Description

      Checking MYFACES-3313 I notice that param defined with f:param inside h:button or h:link has precedence over the same param defined in a faces-config navigation rule. The curious part is the code has this comment:

      // In theory the precedence order to deal with params is this:
      // component parameters, navigation-case parameters, view parameters
      // getBookmarkableURL deal with this details.

      It seems components parameters and navigation-case parameters are handled on the link, but still it is true that getBookmarkable should deal with the remaining stuff.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Leonardo Uribe
            Reporter:
            Leonardo Uribe
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development