Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.0, 2.0.1, 2.0.2
-
Component/s: Framework
-
Labels:None
-
Environment:Windows XP, UnixAIX
Tomcat6
-
Assignee Priority:P2
-
ICEsoft Forum Reference:
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
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)
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
-
ICE-7119 REGRESSION: springsecurity3-login fails to render text on chrome and firefox
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Looks like even in plain JSF deployments with AJAX enabled submission the page rendered after navigation and reload is the index page.
Show
Mircea Toma
added a comment - Looks like even in plain JSF deployments with AJAX enabled submission the page rendered after navigation and reload is the index page.
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.