Zhong Li wrote: > Hi All, > > I am trying to find a way to avoid saveState tag on client side, finally > I got an idea, please give me comments regardless my thought wrong or > right. Actually it is way to save server side data/model. We define > DataSaveManager to manage save/remove a data in a session. When code > saves data into session, sametime need set possible pages the data will > be used, or create a data path rules. In phaseListener after > RENDER_RESPONSE(6), we check the data in session, if current viewRoot > isn't in possible pages list or data path rules list, the data will be > removed automatically. Of couse, code can remove any data anytime. If > the way works, we may find a way to do it in config file. We can add > possiblePageList in ManageBean defination section and pageRuleList in > Navigation Rules section.
All I can say is do not spend too much work into this issue, others have solved the problem for you check out Shale Dialog and Seam, if you do not like x:saveState.
