That's exactly the code I was looking at, assuming you meant "transient" rather than "immediate," which is what got me wondering.
Up to this point, I always thought it was the responsibility of saveState/restoreState to check transient, but now I'm thinking that I've been doing it wrong. Thanks! On 12/2/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > On lookup, I see that there is nothing. I do remember a discussion > about this at some time, though. But that's a long time ago, maybe I > am wrong. > > You don't need to change behaviour - if you look into UIComponentBase, > you see that based on the value of immediate saveState/restoreState > will be called or not. > > regards, > > Martin > > > > On 12/1/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > On 12/1/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > > > @1: yes, I have sometimes thought about this as well - saying that a > > > certain part of the page is exempt from state saving might be nice. > > > There was this transient attribute once for components, but hasn't it > > > been deprecated? > > > > I don't see anything transient being deprecated. One thing I wonder > > about is whether the saveState/restoreState method code needs to > > explicitly change behavior based on the value of transient, or if it's > > always the responsibility of the caller to check the transient value. > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
