...six months later Mark, could you please describe the work-around with re-queuing INVOKE APPLICATION/UPDATE MODEL. Where (lifecycleListener?) and how to do it right? And what about the "enhancement to help developers side-step this issue"?

Ok, let's say you have a rowSelector and input components, and need the rowSelector's selectionListener to be called in INVOKE_APPLICATION, so that the input components' submittedValues will be pushed into the bean, in UPDATE_MODEL, before the selectionListener is called.

The original solution was to do:

public void selectionListener(RowSelectorEvent event) {
if(!event.getPhaseId().equals(javax.faces.event.PhaseId.INVOKE_APPLICATION))

// Now do your processing
}

Then we added a feature to rowSelector, where you could set immediate="false" on it, and the selectionListener would be called in INVOKE_APPLICATION for you, without the re-queue code.

But, for other components, like input components and their valueChangeListener, there was no easy way of having them be called in INVOKE_APPLICATION. In ICEfaces 1.8 RC1 we introduced the ice:setEventPhase component, which is the general solution for changing what phase events will be broadcast in, and so the phase the listeners will be invoked in. You can still use immediate, but setEventPhase makes it unnecessary.

Actually I had the problem with BooleanCheckboxes in the <ice:dataTable>. If the underlying model changed (values were get and set properly), and the number of checkboxes stayed the same the view didn't reflect the model. I hacked it temporary by adding the valueChangeListener like:

public void valueChangeListener(ValueChangeEvent event){
if(!event.getPhaseId().equals(javax.faces.event.PhaseId.INVOKE_APPLICATION))

HtmlSelectBooleanCheckbox checkbox = (HtmlSelectBooleanCheckbox) event.getSource();
checkbox.setId("checkbox" + checkboxId++); //change of id forces icefaces to redraw the component
}

Is there any other (proper) way to force the icefaces to redraw the component? I know that ASP.NET controls have Render() method.

The components are already redrawing themselves. As this Jira explains, the problem is that the UIData containers are storing the old values for the components. You have to call getSavedChildren().clear() on the UIData/UISeries parents if you update your model values.

To Wladyslaw Bultrowicz, immediate="false" on row selector didn't resolved your problem?
In our master-detail view it helps.