The saveState mechanism uses the Serializable features of Java-Objects
- so all that gets serialized will be stored - it's as easy as that.
If you need special features, you can always overwrite the
Serialization/deserialization process.
regards,
Martin
On 5/19/05, Enrique Medina <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I want to save the state of my JSF bean object into the client, due to
> session memory constraints. I can use:
>
> <x:saveState value="#{myBean}" />
>
> But what happens if my bean has a reference to anocher object, that in
> turn has a reference to another object, and so on?
>
> The tag above won't save the state for the references, will it?
>
> So I have to do something like this:
>
> <x:saveState value="#{myBean}" />
> <x:saveState value="#{myBean.object1}" />
> <x:saveState value="#{myBean.object1.object2}" />
>
> Is this right or is there a better way to achieve this?
>
