I used to "publish" in Eclipse, it just copies the war file and the app.
is reinitialized and the session is lost.
This may be a bit off-topic here, as it is a generic container problem,
but it directly affects my evaluation of Wicket.
Should I configure anything on my web.xml or in JBoss files? I didn't
found anything when searching for this.
Note that I most worry about this in production, and not in development.
Adriano
Martijn Dashorst escreveu:
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 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
