saveState vs. inputHidden

[Ken <ke...@gmail.com>]

I agree that saveState is a great asset to MyFaces. You can store whole 
classes between requests and it doesn't have to be nested between form tags. 
Beyond this, does anyone know how it's any different then inputHidden?

Re: saveState vs. inputHidden

[Martin Marinschek <ma...@gmail.com>]

in inputHidden, you can store a value - like a string, a number or
anything you can apply a converter to. It's very close to an
outputText in this relation.

with saveState, you can store whatever you can reach with a
value-binding - it is then serialized to the client side or server
side session and reread/reloaded upon posting back the value to the
server.

regards,

Martin

On 9/2/05, Dennis_Byrne@ak.blm.gov <De...@ak.blm.gov> wrote:
>  
> inputHidden is only the JSF equivalent of <input type="hidden"> .  It
> couldn't hold a candle to t:saveState. 
>  
> Dennis Byrne
>  


-- 

http://www.irian.at
Your JSF powerhouse - 
JSF Trainings in English and German

Re: saveState vs. inputHidden

[De...@ak.blm.gov]

inputHidden is only the JSF equivalent of <input type="hidden"> .  It 
couldn't hold a candle to t:saveState.

Dennis Byrne