ICEfaces
  1. ICEfaces
  2. ICE-1741

submittedValue of component remains stored during page navigation

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.3, 1.6DR#5
    • Fix Version/s: 2.0-Alpha3, 2.0.0
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      any
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      created a simple test case:

      - pageA contains inputText and commandButton to navigate to pageB
      - pageB contains outputText to show inputText's value from pageA and commandButton to navigate back to pageA
      - both the inputText and outputText components are bound to the same backing bean

      only if the standardRequestScope context-param is set to true in web.xml, the submittedValue is cleared when the user navigates back to pageA
      Show
      created a simple test case: - pageA contains inputText and commandButton to navigate to pageB - pageB contains outputText to show inputText's value from pageA and commandButton to navigate back to pageA - both the inputText and outputText components are bound to the same backing bean only if the standardRequestScope context-param is set to true in web.xml, the submittedValue is cleared when the user navigates back to pageA

      Description

      during page navigation, the submittedValue of inputText components is not cleared.
      this is only possible when the standardRequestScope context parameter in web.xml is set to true.
      if there are any validation errors and the user navigates back to the original page, the old submittedValues
      are still remaining. usually one would expect the submittedValues always to be cleared when a real navigation
      is initiated to another page

        Issue Links

          Activity

          Hide
          Mircea Toma added a comment -

          Fixed as a side-effect when fixing ICE-2189. Forward navigation rules now force a page reload which in turn re-creates the request map.

          Show
          Mircea Toma added a comment - Fixed as a side-effect when fixing ICE-2189 . Forward navigation rules now force a page reload which in turn re-creates the request map.
          Hide
          Mircea Toma added a comment -

          Stop propagating attributes between page reloads.

          Show
          Mircea Toma added a comment - Stop propagating attributes between page reloads.
          Hide
          Ken Fyten added a comment -

          Re-opening as the fix for this causes backward-compatibility issues and must be reverted for the 1.7 release.

          Show
          Ken Fyten added a comment - Re-opening as the fix for this causes backward-compatibility issues and must be reverted for the 1.7 release.
          Hide
          Ken Fyten added a comment -

          Need to replace the current extended Request scope with Std. Request scope behavior + a new scope.

          Show
          Ken Fyten added a comment - Need to replace the current extended Request scope with Std. Request scope behavior + a new scope.
          Hide
          Mircea Toma added a comment -

          The code area needing to be changed (ServletExternalContext.class) to fix this issue will reside in JSF 2.0.

          Show
          Mircea Toma added a comment - The code area needing to be changed (ServletExternalContext.class) to fix this issue will reside in JSF 2.0.

            People

            • Assignee:
              Mircea Toma
              Reporter:
              Michael Thiem
            • Votes:
              10 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: