Hi, You could also override the readResolve method of your application scoped bean to reflect its singleton status. However that does create an annoying dependency since the application scoped bean will knows its managed bean name. But if you're using @ManagedBean or @Named, it already does anyway.
Regards, ~ Simon On Sun, Jan 17, 2010 at 3:18 PM, Michael Kurz <[email protected]> wrote: > Jakob Korherr schrieb: > > Hi Michael, >> >> I guess that is the expected behavior... >> >> Also: isn't this serialize and deserialize behavior the same if you use a >> session bean with a reference to an application bean? At least at the time >> when the session is serialized (e.g. cluster with session replication).. >> > > Sure, it is (and was) the same in this case but for the view scope it will > affect more applications I guess. > > - > Michael >
