Thanks for replying so quickly. I think you misunderstood. Maybe because my previous post "independent apps" make you confuse. I apology first. My "independent apps" are , in fact , different pages. They are under the same WEB-APP , maybe share the same user-base. They just process different calculation , saving user's preference in session (not to DB). For example , In PageA , panelA1 is minimized , panel A2 is maximized , In PageB , panelB1 is maximized , panelB2 is minimized ...etc.
My question is , if I don't want to use HttpSession (string property is error-prone) I prefer the wicket way. I found if I go the wicket way , it results in the "composite session object" , it is correct ? PageAsetting settingA = ((MySession)getSession()).getPageAsetting(); PageBsetting settingB = ((MySession)getSession()).getPageBsetting(); Just like the above codes... I have to associate each page's setting object to a root session object (MySession). Yes , it works fine... but ... If I have more pages , more settings , I have to "hook" these setting objects to the root session object . Is it what wicket's favorable way ?
