> 1) <t:aliasBean> reference in RESTORE_VIEW phase
For this case it looks like t:aliasBean, when restoring its state, will evaluate the bean expression.
> 2) <h:component renrered> reference in APPLY_REQUEST_VALUES phase
The rendered attribute has to be evaluated in order to determine whether or
not the component should be decoded.
So this leads back to my original suggestion. Partition your beans such that those
with expensive logic aren't referenced in attributes that will be evaluated at several
points in the lifecycle such as the 'rendered' attribute. It seems the same holds true
for those that are referenced by t:aliasBean due to how it restores state.
[Message sent by forum member 'rlubke' (rlubke)]
http://forums.java.net/jive/thread.jspa?messageID=343413