Hello,
Today I tested an application on a number of computers (if it's useful know
that they were in the same network).
What I found out is that the wicket session was shared among them when
wicket was started in dev mode. When I started the application in deploy
mode, everything was as needed -
No, that is not how it is supposed to work. Each user should always
get his/her own session regardless.
development mode is for quick reloading of markupfiles etc without redeploying.
Not sure how you managed that but we use dev mode all the time and we
have never seen this behavior.
Maurice
On
On Tue, May 20, 2008 at 3:55 AM, Cristi Manole [EMAIL PROTECTED] wrote:
Hello,
Today I tested an application on a number of computers (if it's useful know
that they were in the same network).
What I found out is that the wicket session was shared among them when
wicket was started in dev
well, i figured it was just me... so I quit bothering you guys with
something that's ... just me... :)
i'm using tomcat, no clustering.
this is my websession class:
package com.fx.core;
import java.security.NoSuchAlgorithmException;
import org.apache.commons.logging.Log;
import
do the two users have different session ids? try printing it out from
your authenticate method.
-igor
On Tue, May 20, 2008 at 7:59 AM, Cristi Manole [EMAIL PROTECTED] wrote:
well, i figured it was just me... so I quit bothering you guys with
something that's ... just me... :)
i'm using
no, nothing fancy there...
anyways, I can't seem to replicate it easily now and I don't have time for
further investigation.
sorry for your time and also thank you for it.
i will definitely try later.
On Tue, May 20, 2008 at 8:59 PM, Igor Vaynberg [EMAIL PROTECTED]
wrote:
also, what does
