ICEfaces
  1. ICEfaces
  2. ICE-5401

Initial page rendered on page reload after forward navigation executed when concurrentDOMViews = true

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 1.8, 1.8.2-EE-GA
          • Fix Version/s: 1.8.2-EE-GA_P01, 1.8.3
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            All
          • Workaround Exists:
            Yes
          • Workaround Description:
            Set concurrentDOMViews to false

            Description

            When page is reloaded after navigating using forward navigation rules, instead of reloading the last view ID determined by the navigation rules the initial view ID is rendered.

            This issue was fixed with ICE-3691 but doesn't seem to be fixed when concurrentDOMViews is set to true.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Deryk Sinotte added a comment -

              Assigning to Mircea.

              Show
              Deryk Sinotte added a comment - Assigning to Mircea.
              Hide
              Permalink
              Isuru Perera added a comment -

              I think this issue is caused by disposing views on page reload. There is a Javascript function onbeforeunload to call dispose views.

              On page reload, views are disposed and "MultiViewServer" creates a new view.

              Show
              Isuru Perera added a comment - I think this issue is caused by disposing views on page reload. There is a Javascript function onbeforeunload to call dispose views. On page reload, views are disposed and "MultiViewServer" creates a new view.
              Hide
              Permalink
              Mircea Toma added a comment -

              Views are not reused on page reload when concurrentDOMViews is enabled. This is the expected behavior since 1.6 release.
              See: http://www.icefaces.org/docs/v1_8_2/htmlguide/devguide/keyConcepts11.html
              and http://jira.icefaces.org/browse/ICE-3907?focusedCommentId=23848&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_23848 .

              Show
              Mircea Toma added a comment - Views are not reused on page reload when concurrentDOMViews is enabled. This is the expected behavior since 1.6 release. See: http://www.icefaces.org/docs/v1_8_2/htmlguide/devguide/keyConcepts11.html and http://jira.icefaces.org/browse/ICE-3907?focusedCommentId=23848&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_23848 .
              Hide
              Permalink
              Ted Goddard added a comment -

              Obtaining a new component tree on page reload is standard JSF behavior.

              Show
              Ted Goddard added a comment - Obtaining a new component tree on page reload is standard JSF behavior.
              Hide
              Permalink
              Isuru Perera added a comment -

              Even though this is the standard behavior, I had few issues after reloading the page when concurrentDOMViews is set to true.

              The issue was caused by the dispose views handler..

              In my application, after a reload, correct pages were not displayed.

              Suppose there are two pages, "edit" and "view". Both pages are displayed after a "search" page.

              Initial search page navigation is a redirect, and therefore "search" url is displayed. Then I search and go to a "view" page (No redirect here). Then I reload the page. Search page is displayed (Default behavior). But hereafter navigation to edit page won't work. No redirect to edit page also.

              This happens when the url get "rvn=" parameter. If I reload the page when the url has "rvn=" parameter, navigation to that same page doesn't work. What happens is that initial view is displayed. In my case it is the search page.

              All these issues were causing as the views were disposed as soon as I reload the page. All the views are removed.

              I don't have much time to explain in detail and I hope you understood what I say.

              I will comment again later.

              Show
              Isuru Perera added a comment - Even though this is the standard behavior, I had few issues after reloading the page when concurrentDOMViews is set to true. The issue was caused by the dispose views handler.. In my application, after a reload, correct pages were not displayed. Suppose there are two pages, "edit" and "view". Both pages are displayed after a "search" page. Initial search page navigation is a redirect, and therefore "search" url is displayed. Then I search and go to a "view" page (No redirect here). Then I reload the page. Search page is displayed (Default behavior). But hereafter navigation to edit page won't work. No redirect to edit page also. This happens when the url get "rvn=" parameter. If I reload the page when the url has "rvn=" parameter, navigation to that same page doesn't work. What happens is that initial view is displayed. In my case it is the search page. All these issues were causing as the views were disposed as soon as I reload the page. All the views are removed. I don't have much time to explain in detail and I hope you understood what I say. I will comment again later.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Arran Mccullough
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: