Yeah, I think you're better off just preserving the entire OrderBacker.
It's not really request-scope, but page-scope.
On 9/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Mike Kienenberger <[EMAIL PROTECTED]> wrote on 09/07/2005 09:07:01 AM:
>
> > Is there a reason why you dont preserve your OrderBacker backing bean
> > with t:saveState?
>
> I just hadn't had the need until now. My usual is to contruct a graph of
> objects in an action and let JSF's Apply Request Values handle the
> *RE*construction of this for each request cycle.
>
> One solution that I am not too thrilled about at this point is to change the
> value binding to something that like #{OrderBacker.zipCodeHack} . As you
> know, the JSF infrastructure would create the base, allowing state to be
> preserved using t:saveState w/out running into a null base exception.
> Although this uses t:saveState w/ more precision, it complicates the backing
> bean. For example, what if there needs to be 10 values preserved?
