Yeah, it's worth noting that inputHidden and saveState are very similar in behavior when used like this.
On 1/5/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > >So, in cases where I need to output something, I know I'll have it > >there. Isn't what you're talking about only an issue if I go from a view > >with an input component to one that expects to display the input value, > >rather than validation returning to the same view that has the input > >component? > > What I mean is, the inputHidden trick is good at "recycling" the value across > requests. JSF ushers it back and forth between the model and the rendered > output. But when a validation error occurs, during the process validation > phase (3), the request goes straight to render response (6) - w/out the > update model phase. Unfortunately there are things in your view that render > based upon model values (input fields in 'edit' mode, plain text in 'view' > mode). This affects other things, like your [EMAIL PROTECTED], which would > probably be blank if you weren't using that crazy Shale stuff ;) > > >
