Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: EE-4.0.0.GA
-
Fix Version/s: 4.2
-
Component/s: MOBI-Components
-
Labels:None
-
Environment:jsf2.2 mobi
-
Workaround Description:all beans for the mobi:view must be SessionScoped at current time.
Description
The current showcase example has examples which are all SessionScoped beans. By changing any of these to @WindowsScoped, if the session expires, a ViewExpiredException is also thrown and this locks up the app. Sometimes you have to restart the server. Other times, the viewManager loses styling and ability to navigate to any other examples (on small device).
To reproduce, change any example bean for mobi to @WIndowsScoped (similar to ace component examples) and let the session expire. Then try to reload the application.
To reproduce, change any example bean for mobi to @WIndowsScoped (similar to ace component examples) and let the session expire. Then try to reload the application.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Tested the scenario with ICEfaces 4 trunk r 49099 using window scoped bean in the flip switch application. After session expiry there were no issues with reloading the application.
Show
Liana Munroe
added a comment - Tested the scenario with ICEfaces 4 trunk r 49099 using window scoped bean in the flip switch application. After session expiry there were no issues with reloading the application.
I tried changing a few of the beans to window scope but I could not reproduce this issue. The ViewExpiredException would show up only when interacting with any of the Mobi demos after the session has expired. The exception would be then properly trapped and re-thrown as a SessionExpiredException.