Michael Youngstrom wrote:
> Sounds like a fun place for an SPI? :) Is there flexibility in the
> spec for custom state saving solutions? I'd vote for that an _05
> addition.
In the faces-config, a developer can specify a custom state manager.
If the custom state manager provides a single arg constructor
that accepts a StateManager, then the default state manager will be
passed to that constructor to allow customization of the default
behavior.
The snag that I see is that the spec doesn't really allow
for easy replacement of the ResponseStateManager (the entity
responsible for writing the state in a mark-up appropriate manner)
without a custom renderkit.
I'm still mulling this over.
>
> Mike
>
> On 2/27/07, Adam Brod <ABrod_at_intralinks.com> wrote:
>>
>> Hi-
>>
>> I am interested in storing my JSF view state in a local cache - not the
>> session nor client side. Is this very difficult to do? Is there a
>> standard
>> hook that I can implement to do this? Or would I need to hack around
>> in the
>> RI code?
>>
>> Thanks for any tips.
>>
>> Adam Brod
>> Product Development Team
>> Disclaimer: This electronic mail and any attachments are
>> confidential and
>> may be privileged. If you are not the intended recipient, please
>> notify the
>> sender immediately by replying to this email, and destroy all copies
>> of this
>> email and any attachments. Thank you.
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_javaserverfaces.dev.java.net
> For additional commands, e-mail: users-help_at_javaserverfaces.dev.java.net
>