On Tue, 2006-01-24 at 23:28 +0000, Dennis Byrne wrote: > >To sum it up, no you should implement serializable if possible > >due to inherent problems with web containers, which often do not like > >non serializable objects anymore, at least for objects which you want to > >keep longer than a single request. > > I agree. It is also less painful when your project goes from server to > client side state saving during the middle of a project. >
But this only applies when the backing bean is not of request scope. For beans of session/app scope I agree that they should be Serializable even if the application is not *currently* clustered, as it might be in the future. For a backing bean that is of request scope and is not referenced by a <t:saveState> I see no reason for that class to be Serializable. Regards, Simon
