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
and shut down your app server in a normal way :). Kill -9 doesn't give
the server a chance to write things to disk (as does the little red
button in eclipse)
Martijn
On Fri, Sep 26, 2008 at 8:42 AM, Johan Compagner [EMAIL PROTECTED] wrote:
For wicket you shouldnt have to do anything except
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.
