Hi,
Thanks for the quick reply. That would mean that the second level cache
isn't used any more right? Does this lead to a great increase in session
size or are there other disadvantages?
Regards,
Ivo
On 6/20/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 6/20/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> you either have to pass a reference, keep a reference to last page in
> session, or not use the second level page store.
If you put:
protected ISessionStore newSessionStore() {
return new HttpSessionStore(this);
}
in your application object, Wicket will use that session store instead
of the default. HttpSessionStore is the same store as was the default
in 1.2.
Eelco
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
