Data_table inspects "value" before other inputs are processed.

Question

Hello,
The ordering in which JSF processes inputs and outputs in the presence of a data_table seems problematic, and I'm at a loss for a workaround.
When a form is submitted (via a command_button, for example), the data_table accesses its "value" reference before any of the other "inputs" in the form are processed by JSF. For example:
[snip]
<h:input_text value="#{TestBean.testValue}"/>
<h:data_table rows="2" value="#{TestBean.result}" var="object">
<h:column>
<f:facet name="header">
<h:output_text value="Name"/>
</f:facet>
<h:output_text value="#{object.name}"/>
</h:column>
</h:data_table>
<h:command_button action="#{TestBean.testAction}" value="Test"/>
[snip]
When this form is submitted, the value from input_text is set AFTER data_table calls TestBean.result. So, the ordering of method calls after submission is:
TestBean.result
TestBean.testValue
TestBean.testAction
In contrast, if a data_table is NOT used to get at TestBean.result, the ordering of the method calls is quite different:
TestBean.testValue
TestBean.testAction
TestBean.result
Is this a bug, or does data_table intentionally inspect its "value" before any of the other form inputs are processed? If so, what is the solution for ensuring TestBean gets all of the information it needs before TestBean.result is called in the data_table...? In other words, TestBean.result depends on TestBean.testValue.
Please let me know if any other info is needed!
Thanks,
Ryan

Answer 1

Hi Adam,
Thanks for your reply. I guess I could use some help making the leap from Controller/View mentalities. :)
How can a bean ever process input data if it can't depend on the data being there? Or, can you suggest a way to model the above example so that the "results" getter always knows the input from "testValue" has been set -- split it into two beans maybe?
Or, maybe do the processing inside the "testAction" instead of "results"? Even then, wouldn't that be assuming that when "testAction" is called, "testValue" has been set.
I'm afraid I don't understand how this can be modeled without some expectation that form values have been filled in the bean before other tasks are fired.
Thanks,
Ryan