Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: EE-3.0.0.BETA, 3.0.1
-
Component/s: Documentation, Framework, ICE-Components, Sample Apps
-
Labels:None
-
Environment:ICEfaces 3 ICEpush
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
Under certain conditions I am seeing the following exception:
Caused by: java.io.NotSerializableException: org.icefaces.application.PushRenderer$2
To replicate I:
1) Deploy and run the ACE Showcase
2) Choose the ace:progressBar > Push example and run the progress bar
3) Shut down Tomcat and restart it (which should serialize/deserialize the current session)
It seems that the LongTaskManager class is a window-scoped bean used in the noted example and that it keeps a reference to a PortableRenderer - an anonymous inner class of PushRenderer - and the inner class is not Serializable. This is by design.
Simply marking the "private PortableRenderer renderer" instance as transient has side effects that break the proper operation of the progress bar.
Caused by: java.io.NotSerializableException: org.icefaces.application.PushRenderer$2
To replicate I:
1) Deploy and run the ACE Showcase
2) Choose the ace:progressBar > Push example and run the progress bar
3) Shut down Tomcat and restart it (which should serialize/deserialize the current session)
It seems that the LongTaskManager class is a window-scoped bean used in the noted example and that it keeps a reference to a PortableRenderer - an anonymous inner class of PushRenderer - and the inner class is not Serializable. This is by design.
Simply marking the "private PortableRenderer renderer" instance as transient has side effects that break the proper operation of the progress bar.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion