> > I don't understand what's your problem. Page activation context would >> always be kept between any requests of the same page, if you add the context >> that given to the tab component tot he page activation conetext, and provide >> the correct onActivate and onPassivate handler, there would be no problem at >> all. Everything should work. >> > > with onPasivate() you are totally right although it forces to set additional context value and onPassivate() at each page that uses the controller and contextfield needs to be @persist-ed in session. Contrary to that when you pass context value(s), while in page's onActive(..) , to component and then redirect with *pagerender.createPageRenderLinkWithContext * then at least the field can be persisted using flash type and you dont need additional code.
Everything right, as long as the context value is passed to the tab > component. > It seems to me that the tab state is not preserved between requests. > > yes it is not, and what I noticed is that when using onPassivate then the action link gets ?t.ac=context_value so someone there has been thinking about that but went wrong way :| (at least in my opinion) The session itself is extremely overused in the framework and it could be limited if only actionLink's call preserve page's context. that are my thoughts about that and maybe I just think in wrong way.... -- pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski....@gmail.com ______________________
