|
Simon, indeed the bean is request-scoped and yes, uiCheckedSelector
is initialized to false. But this is quite normal AFAIK. I would expect
that the update model phase should properly set the value to true, if
coming from a page where the checkbox was checked. Then it should
notice that value has changed and fire an event. The debugger sequence after checking is: - isUiCheckedSelector(); // returns false - checkedChanged(); // ==> event - setUiCheckedSelector(true); - isUiCheckedSelector(); // rendering: returns true while after unckecking is: - isUiCheckedSelector(); // returns false - setUiCheckedSelector(false); - isUiCheckedSelector(); // rendering, returns false Ok, setting immediate to "true" was a mistake in this context (to get the model properly updated), but even after removing it nothing changed. Indeed, it seems that a decision about event firing occurs *before* updating the model, thus using always model defaults for comparison. -- Renzo Simon Kitching wrote: Hi Renzo, |
- Re: selectBooleanCheckbox not calling the listener Renzo Tomaselli
- Re: selectBooleanCheckbox not calling the listener Renzo Tomaselli
- Re: selectBooleanCheckbox not calling the listene... Renzo Tomaselli

