ICEfaces
  1. ICEfaces
  2. ICE-6927

Refreshing a page redirects to index page

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0.0, 2.0.1, 2.0.2
          • Fix Version/s: 2.1-Beta, 3.0
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Windows XP, UnixAIX
            Tomcat6

            Description

            After refreshing a webpage by pressing F5, the application is redirected to index page.
            The session settings are kept well but you have to navigate to the position you've refreshed.
            The problem was observed after migrating from ICEFaces 1.8 to ICEFaces 2.0 and is still present in current release (2.0.2)

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-7119 REGRESSION: springsecurity3-login fails to render text on chrome and firefox

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                5 older comments
                Hide
                Permalink
                Greg Dick added a comment -

                See above comment on redirection navigation cases.

                Show
                Greg Dick added a comment - See above comment on redirection navigation cases.
                Hide
                Permalink
                Ted Goddard added a comment -

                This feature makes use of the "safe" aspect of window scope (propagation only, not disposal). So, if we have a variant of windowScope without the onBeforeUnload POST, this should continue to function.

                Show
                Ted Goddard added a comment - This feature makes use of the "safe" aspect of window scope (propagation only, not disposal). So, if we have a variant of windowScope without the onBeforeUnload POST, this should continue to function.
                Hide
                Permalink
                Mircea Toma added a comment - - edited

                Introduced "org.icefaces.replayNavigationOnReload" context parameter to allow the disabling of the non-standard (but useful) behaviour. The parameter's value defaults to "true".

                Show
                Mircea Toma added a comment - - edited Introduced "org.icefaces.replayNavigationOnReload" context parameter to allow the disabling of the non-standard (but useful) behaviour. The parameter's value defaults to "true".
                Hide
                Permalink
                Mircea Toma added a comment -

                Turning off navigation replay by default.

                Show
                Mircea Toma added a comment - Turning off navigation replay by default.
                Hide
                Permalink
                Mircea Toma added a comment -

                Changing ReloadAfterNavigationFix navigation handler to bring navigation behaviour closer to the standard JSF behaviour proved impossible to achieve.
                When non-redirect navigation and redirect navigation rules are mixed it's not possible to determine with certainty if a request is just for page reload or a request for loading a different page.

                For example when page A is loaded and a non-redirect navigation is made to page B all the forms in the rendered page have now page B's url. If we reload page A ReloadAfterNavigationFix navigation handler will make sure the navigation is replayed and B's content is shown again. If we click on a command link with AJAX disabled the requested page is B because the forms use B's url now, so it's impossibile to determine now that what the user really wanted was page A content rendered.

                The compromising solution was to make the replay navigation feature configurable. There are applications or environments (like portals) that use only non-redirect navigation rules. These application become much more natural to use once replay navigation feature is introduced.

                Show
                Mircea Toma added a comment - Changing ReloadAfterNavigationFix navigation handler to bring navigation behaviour closer to the standard JSF behaviour proved impossible to achieve. When non-redirect navigation and redirect navigation rules are mixed it's not possible to determine with certainty if a request is just for page reload or a request for loading a different page. For example when page A is loaded and a non-redirect navigation is made to page B all the forms in the rendered page have now page B's url. If we reload page A ReloadAfterNavigationFix navigation handler will make sure the navigation is replayed and B's content is shown again. If we click on a command link with AJAX disabled the requested page is B because the forms use B's url now, so it's impossibile to determine now that what the user really wanted was page A content rendered. The compromising solution was to make the replay navigation feature configurable. There are applications or environments (like portals) that use only non-redirect navigation rules. These application become much more natural to use once replay navigation feature is introduced.

                  People

                  • Assignee:
                    Mircea Toma
                    Reporter:
                    Jörg Jansen
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: