Details

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

      Operating System: All
      Platform: All

    • Issuezilla Id:
      484
    • Status Whiteboard:
      Hide

      EGTop5 effort_hard

      Show
      EGTop5 effort_hard

      Description

      Navigation rules which perform redirects should be able to specify a list of
      request parameters to use in the redirect (where the parameter values are
      defined using value expressions)

        Issue Links

          Activity

          pmuir created issue -
          Hide
          pmuir added a comment -

          Blocks 455

          Show
          pmuir added a comment - Blocks 455
          Hide
          pmuir added a comment -

          Conversely, any incoming request parameters should be applied to the model using
          these mappings. These model updates need to be converted and validated as JSF
          would do for POST requests. I would suggest nesting a validator, for example:

          <navigation-rule>
          <from-action>#

          {customerFinder.findByName}

          </from-action>
          <navigation-case>
          <to-view-id>/displayCustomer.xhtml</to-view-id>
          <redirect>
          <parameter-name>customerId</parameter-name>
          <parameter-value>#

          {customerFinder.result.id}

          </parameter-value>
          <validator-id>fooValidator</validator-id>
          <converter-id>fooConverter</converter-id>
          </redirect>
          </navigation-case>
          </navigation-rule>

          Show
          pmuir added a comment - Conversely, any incoming request parameters should be applied to the model using these mappings. These model updates need to be converted and validated as JSF would do for POST requests. I would suggest nesting a validator, for example: <navigation-rule> <from-action># {customerFinder.findByName} </from-action> <navigation-case> <to-view-id>/displayCustomer.xhtml</to-view-id> <redirect> <parameter-name>customerId</parameter-name> <parameter-value># {customerFinder.result.id} </parameter-value> <validator-id>fooValidator</validator-id> <converter-id>fooConverter</converter-id> </redirect> </navigation-case> </navigation-rule>
          Hide
          pmuir added a comment -

          A JBoss top priority issue issue

          Show
          pmuir added a comment - A JBoss top priority issue issue
          Hide
          Ed Burns added a comment -

          Change target milestone to 2.0

          Show
          Ed Burns added a comment - Change target milestone to 2.0
          Hide
          Ed Burns added a comment -

          fixed in 2.0

          Show
          Ed Burns added a comment - fixed in 2.0
          Hide
          Ed Burns added a comment -

          Prepare to delete "spec" subcomponent.

          Show
          Ed Burns added a comment - Prepare to delete "spec" subcomponent.
          kenaiadmin made changes -
          Field Original Value New Value
          issue.field.bugzillaimportkey 484 20089
          made changes -
          Hide
          Manfred Riem added a comment -

          Closing resolved issue out

          Show
          Manfred Riem added a comment - Closing resolved issue out
          Manfred Riem made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              javaserverfowner
              Reporter:
              pmuir
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: