Oh, now I see what you're saying. That's pretty subtle! I'm glad that it wasn't a more sinister reason. ;-)
- Brendan -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Friday, September 09, 2005 3:38 PM To: MyFaces Discussion Subject: Re: understanding the impact of 'rendered' Doing a saveState on employeeAction.editMode or employeeAction should preserve it. On 9/9/05, Rick Reumann <[EMAIL PROTECTED]> 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 >
