Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.2.GA_P02
-
Fix Version/s: EE-1.8.2.GA_P03
-
Component/s: Facelet Components
-
Labels:None
-
Environment:Clustered Environment
Description
Issue reported from customer:
"When I perform a search and fill in a AutoSortTable component, and right after stop the cluster instance, the session of the application gets replicated to the other instance but the AutoSortTable component becomes empty.
I have declared the AutoSortTableBean object as transient because otherwise it gives me error on the object not being Serialized."
If the AutoSortTableBean can be serializable then the data used in the component should persist to the new cluster instance.
"When I perform a search and fill in a AutoSortTable component, and right after stop the cluster instance, the session of the application gets replicated to the other instance but the AutoSortTable component becomes empty.
I have declared the AutoSortTableBean object as transient because otherwise it gives me error on the object not being Serialized."
If the AutoSortTableBean can be serializable then the data used in the component should persist to the new cluster instance.
Revision #25168
In a previous issue related to clustered deployment and session scope beans I implemented Serializable on all the session scope beans in the faces-config.xml file included in the composite component jar.
The issue here appears to be that there are some classes that can be instantiated by the client and included as member variables of their session scope beans.
To avoid any further issues around this problem, I have implemented Serializable on all the classes in the composite component jar.
This has already been done in the 2.0 version.