I think you should differentiate between the state of the component and the value binded to the component. The state is stored in session (if server) and as hidden fields (in client), so I don't think you will face problems with that.
Maybe your question is more about the value of the components, which is usually binded to a backing bean that, if request scoped, is recreated in each new request (so the value is lost from request to request). If you need to preserve the value from request to request then you should bind your value to the session or have a look at the Dialogs from Shale (there has been a lot of discussion about the scope in this forum).
Hope it helps,
Enrique Medina.
2005/7/21, Galen Dunkleberger <[EMAIL PROTECTED]>:
Am I correct in believing a component only holds its state for the
life of a single view. So that if the "same" component is in two
differenet views and I navigate from one view to other the component
will not retain it's state from the previouse view without it's values
or itself being bound to a session scoped managed-bean? Or is it
possible for a component to save it's own state acrossed multiple
views?
Thanks,
Galen
