Hi Renzo,
MyFaces certainly performs a depth-first walk of the component tree when
processing any JSF phase. This effectively means that components are
processed in the order they are defined in your page layout.
I would expect that every JSF implementation will do the same, though if
you are concerned about portability I suggest you read the Sun javadocs
for classes like UIComponent to see whether they actually require this
behaviour; I think they do but haven't checked.
Regards,
Simon
Renzo Tomaselli 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
