only wicket pages get serialized at the end of each request, not the entire http session. the session is serialized by the servlet container during session passivation or replication.
-igor On Tue, Dec 15, 2009 at 11:57 PM, Janning Vygen <[email protected]> wrote: > Hi all, > > i am using wicket for a few days. It is great! My first question: > > I tried some simple authorizations like described in WIA. > > this is part of my custom Session: > > public class AuthenticatedWebSession extends WebSession > { > private User user; > public void setUser ( User user ) > { > bind(); > this.user = user; > } > } > > User is a persistableEntity managed by Hibernate. User is NOT Serializable. > But if i run it, i do not get any SerializableExceptions. But the session gets > serialized at the end of the requestcycle? So user must get serialized too? > > Why does it work without an SerializationException? > > kind regards > Janning > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
