Hi, you can also put the whole bean in t:saveState. This may prevent you from running into these problems.
cheers, Gerald On 12/5/06, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
Hi all, I use saveState component to transmit persistent values across requests. This implies that a proper bean setter is invoked while restoring a view. Now, it happens that the restored value might influence other tags, both in terms of value model and rendering. The question is: can I count on a specific order in getting all setters called, so that for instance I can force saveState restoring to occur before all other setters ? Does it depend on page layout positioning ? Btw, this is a generic issue concerning alla setters in a bean. Thanks -- Renzo
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
