myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Kienenberger <mkien...@gmail.com>
Subject Re: understanding the impact of 'rendered'
Date Fri, 09 Sep 2005 20:38:20 GMT
Doing a saveState on employeeAction.editMode or employeeAction should
preserve it.

On 9/9/05, Rick Reumann <r@reumann.net> wrote:
> Mike Kienenberger wrote the following on 9/9/2005 4:26 PM:
> > Yes, that's exactly what I'm saying.
> > At the start of every phase for every component, the result of
> > isRendered() is computed.  If it's false, nothing happens during that
> > phase.
> 
> Ok thanks, I'll have to play around with that and figure out then how I
> make sure
> 
>   rendered="#{!employeeAction.editMode}
> 
> remains true.
> 
> Personally I don't find that behavior that diserable but I'm sure there
> is a reason for it. When you see "rendered," I would think one is simply
> going to think "Here's the condition to decide whether this component is
> visible or not," but obviously there is more to it than that.
> 
> 
> --
> Rick
>

Mime
View raw message