Wicket Page lifecyle management (session perspective)

[Ravi_116 <ra...@gmail.com>]

Our wicket web application uses spring to inject beans into the Page Class.
Our application also has login page with user credentials. The Engine (our
domain service class) class is injected with user credentials.
Unfortunately, the Page class seems to be instantiated only once (even when
logging in as two seperate users). Is there a way to either inject a new
Engine class for same page class or create a new Page per user ?

-- 
View this message in context: http://www.nabble.com/Wicket-Page-lifecyle-management-%28session-perspective%29-tp14430250p14430250.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Wicket Page lifecyle management (session perspective)

[Timo Rantalaiho <Ti...@ri.fi>]

On Wed, 19 Dec 2007, Ravi_116 wrote:
> Our application also has login page with user credentials. The Engine (our
> domain service class) class is injected with user credentials.
> Unfortunately, the Page class seems to be instantiated only once (even when
> logging in as two seperate users). Is there a way to either inject a new
> Engine class for same page class or create a new Page per user ?

Different sessions have different page instances, so 
probably you need to invalidate the Wicket Session in between
the logins. This way you should have exactly one Page 
instance per user.

Best wishes,
Timo


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org