Simon Kitching-4 wrote:
>
> And java's serialization has *always* discarded transient objects on
> serialization and marked them as null on deserialization. That's
> perfectly normal. There are a number of options here for you, including
> transient Bean2 appBean = new Bean2();
> or accessing it only via a getBean2() method that checks whether it is
> null and restores it, or implementing custom serialization for Bean1.
>
Thanks for the reply. My point is that JSF allows injecting an application
scoped bean into a session scoped bean. As this is the only way to give
the latter access to the former without code pollution, this should be
the recommended way suggested by JSF. However, due to the problem
raised above, in fact the recommended way is not really working.
-----
--
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-tp15303767p15326677.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
