On 8/31/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> How's it breaking? The little info that you've provided seems fine.
What's not working is when I get to the 'saveAction' method of my
backingBean the 'id' of the Employee object in my backingBean
(EmployeeAction) is null. I would think that if I did saveState on the
whole EmployeeAction class on the JSP that the id would be there in
the same Employee object that is able to output the id fine in a
hidden field.
> However, you might find it more efficient to do this since you're
> doing the same thing with an hidden field.
>
> <x:saveState id="employee" value="#{employeeAction.employee.id}"/>
But what if I potentially wanted to prreserve a bunch of properties,
not just id? Wouldn't it make sense to saveState on the whole
backingBean?
--
Rick
