The <t:saveState> looks like this:
<t:saveState id="idSaveAddress" value="#{address}"/>
---
JSF config file (for this managed bean) looks like this:
---
<managed-bean>
<managed-bean-name>address</managed-bean-name>
<managed-bean-class>com.disney.bb.address</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
---
Will write a test case so I can actually see the values during during
instantiation (constructor), during setters and just after the setters.
thanks
L
Simon Kitching-3 wrote:
>
> Lisa wrote:
>> I'm not seeing that the values are restored at the beginning. I must
>> have
>> something wrong.
>>
>> I have a BB that has 3 setters called after instantiation. I need the
>> saveState restore to happen before these setters are called but it looks
>> like the values are being restored much later.
>>
>> Is there a way to have the state restored before the setters are called?
>
> The t:saveState bean does its work in the restore-view phase. It will
> therefore definitely happen before any value-binding expressions on JSF
> components are evaluated.
>
> If you are seeing normal setters called during the "update model" phase
> but t:saveState hasn't executed to restore the saved data then you have
> something set up wrong - ie t:saveState is not being processed at all,
> or is updating some variable other than the one you are expecting.
>
> Are you definitely setting the value attribute to a
> value-binding-expression, ie
> <t:saveState value="#{myBean}"/>
> not
> <t:saveState value="myBean"/>
> ?
>
> Regards,
>
> Simon
>
>
--
View this message in context:
http://www.nabble.com/When-does-saveState-occur--tf3177625.html#a8835162
Sent from the MyFaces - Users mailing list archive at Nabble.com.
