On 8/7/05, Werner Punz <[EMAIL PROTECTED]> wrote:
> In my opinion x:saveState is superior to every dialog approach on the
> web, because it keeps things small and simple. You do not need
> another set of page flow syntax files, you just add an x:saveState and
> use the existing page flow syntax of JSF to do your stuff.
> The only culprit I have with x:saveState is, that you definitely have
> your components serializable and thus you have to do extra work for
> complex objects.
I agree. I considered implementing a "page"-scoped Managed Bean
extension, but when I finished defining what I wanted it to do, it was
performing the same operations as x:saveState, yet wasn't as flexible.
However, it was frustrating and time-consuming to learn how to
serialize my page's backing bean (2 hours), but it'll be easier and
faster in the future now that I understand the issues better.
One issue I still haven't adequately solved is how to recreate the
linkages between my backing bean and the other beans.
Currently, I'm doing things like this.
ValueBinding binding =
facesContext.getApplication().createValueBinding("#{authenticationBean}");
authenticationBean = (AuthenticationBean)binding.getValue(facesContext);
binding =
facesContext.getApplication().createValueBinding("#{adminDbDataStore}");
adminDbDataStore = (AdminDbDataStore)binding.getValue(facesContext);
Maybe it's an indication that I need refactor my page-scope backing
bean into multiple beans so that dependencies on other beans no longer
exist.
-Mike
