For wicket you shouldnt have to do anything except making your stuff thats in your session/pages all serializable. The container should take care of the rest
On 9/26/08, Adriano dos Santos Fernandes <[EMAIL PROTECTED]> wrote: > Hi! > > On a non Wicket application running on OC4J, I had the problem of the > HTTP session being lost when the application was redeployed. The usage > of session data was minimum, for authentication purpose. I'd solved the > problem with a custom encrypted cookie that reconstructs the server session. > > This problem seems critical for Wicket application. In this case, I'll > probably use JBoss. Is there any good thing I can do to avoid (or > minimize, i.e., only for changed classes) such type of problem? > > Thanks, > > > Adriano > > > --------------------------------------------------------------------- > 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]
