Hi,
Suppose I have a session scoped bean class Bean1 that refers
to an application scoped bean (Bean2) using a managed property:
public class Bean1 implement Serializable {
private transient Bean2 appBean;
}
The appBean field is marked as transient because as a global object, it is
not
serializable. However, when the Bean1 instance is deserialized, JVM will
create the bean instance and restore the fields using brute force without
calling
constructors or involving JSF. It means the appBean field will be null.
Any workaround? This seems to be a design fault in JSF.
-----
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
--
View this message in context:
http://www.nabble.com/Serialization-issue-with-app-scoped-beans-referenced-by-session-scoped-beans-tp15303767p15303767.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
