Just an idea: you could bind the component itself to a session scoped bean or save that bean with the <x:saveState> component between requests.
I have not tried this, but I guess that should avoid loosing the state between multiple requests even with page navigation.

Reply via email to