Subbu,
If you write a Wicket application you never worry about session
cleanups. Only Wicket puts stuff in the session and only Wickets removes
it again. Wicket really does an excellent job here. I have never found
any reason to tweak this.
That said, you as a programmer have the
Premature optimization. Don't try to do this type of stuff unless it
is actually a problem. Why not make sure you have applications first
and then see if it is actually a problem?
Martijn
On Sat, Mar 14, 2009 at 2:40 AM, subbu_tce subramanian.mur...@gmail.com wrote:
I mean two different wicket
Subbu,
Also, when the session of the first application expires, the pagemap is
automatically deleted. So, you'll only have to wait a few minutes and Wicket
will do the job for you.
-- Cristiano
On Sat, Mar 14, 2009 at 3:38 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
Premature
Sorry if i am being ignorant in posting these kind of questions
But i am in the evaluation of wicket in comparison with a proprietary
framework (currently used for building large scale business applications)
which provides comprehensive session clean up flexibilities thorough XML
do you mean multiply wicket applications on the same host?
(just like our example?)
then yes you have a pagemap set per wicket app in your session (prefixed
with the wicket app name)
There are no such hooks because a wicket app 1 is independent on wicket app
2, they should be isolated.
(they
I mean two different wicket applications running in the same JVM..
And i launch the first wicket application in a window.. i navigate among
different pages in the first wicket application. now since i have navigated
through different pages, i understand that multiple versions of the pages
would
