Re: SV: SV: Multiple wicket applications in a single WAR
Wilhelmsen Tor Iver wrote: The ThreadLocal objects are static, yes, but the actual objects stored there are per thread and thus not static. My thoughts exactly Wilhelmsen Tor Iver wrote: The Application instance is shared between all users, but in this case there is no user state in it, the difference is which Session class is used for factorizing the user Session, and which Pages are mounted (again, for factory purposes). I'm not sure what exactly it is you are asking...? I have a bunch of pages mounted(loging pages for both applications) in my base abstract Application class's init() so both my sub Applications mount the same pages... (could this be it?) Also both my Application implementations specify their own home pages and sign in pages Could there be something wrong in my sessions? I thought it might be some static/synchronisation issue -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Multiple-wicket-applications-in-a-single-WAR-tp3066793p3081633.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
SV: SV: Multiple wicket applications in a single WAR
I don't think it is a good idea to have multiple applications in one war. Wicket stores static state in ThreadLocals (Application, Session, etc.). The ThreadLocal objects are static, yes, but the actual objects stored there are per thread and thus not static. All apps in the same war share the same ClassLoader and thus the same static ThreadLocal instances. There might be circumstances when the state somehow gets messed up. If one thread can get at objects belonging to a different thread that would not be a circumstance but a serious bug. I'm sure this is the source of your problems. So, either go for one app for all users or create two separate war files. The Application instance is shared between all users, but in this case there is no user state in it, the difference is which Session class is used for factorizing the user Session, and which Pages are mounted (again, for factory purposes). - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org