Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P04, 4.2
-
Fix Version/s: EE-4.2.0.GA, EE-3.3.0.GA_P05
-
Component/s: QA
-
Labels:None
-
Environment:jsf2 core
-
Support Case References:Support Case 14136:- https://icesoft.my.salesforce.com/5007000001kswFt?srPos=0&srKp=500
Description
a test application for this feature is required where we can modify the lazy window scope (dynamically?) to show behavior of this feature when using various scoped beans.
For now, @ViewScoped, windows scope and @SessionScoped beans should be part of the test.
For now, @ViewScoped, windows scope and @SessionScoped beans should be part of the test.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Added test case for the replayNavigationOnReload behaviour at qa/trunk/Regression-Icefaces4/Sparkle/Manual/replayNavigationOnReload.
Show
Mircea Toma
added a comment - - edited Added test case for the replayNavigationOnReload behaviour at qa/trunk/Regression-Icefaces4/Sparkle/Manual/replayNavigationOnReload .
Backported fix.
Show
Mircea Toma
added a comment - Backported fix.
Verified ICEfaces 4 trunk r51705, Tomcat 8, MS Edge, IE 11, 10, 9, 8, FF 47, Chrome 59.
EE maintenance branch backport is not yet tested.
Show
Liana Munroe
added a comment - Verified ICEfaces 4 trunk r51705, Tomcat 8, MS Edge, IE 11, 10, 9, 8, FF 47, Chrome 59.
EE maintenance branch backport is not yet tested.
Altered window scope behaviour to keep on tracking the window scope even when there are no window scope beans defined by the application but the context parameter org.icefaces.lazyWindowScope is set to false. This change ensures that replayNavigationOnReload navigation feature will track the navigation state separately for each of the active windows. Previously a (dummy) window scope bean was required to be defined in the application to trigger the described behaviour.