JSF component processing and rendering order

Question

Hi,
I have a request level managed bean that has two list boxes on it.
The first is always displayed, and the second should only ever be displayed when the first one has had a value selected in it.
So, I use something like this:
<h:selectOneListbox styleClass="selectOneListbox" value="#{moveBean.sourceListIndex}" size="1" onchange="javascript:submit();" >
    <f:selectItems value="#{moveBean.sourceLists}" />
</h:selectOneListbox>                               
<h:selectOneListbox styleClass="selectOneListbox" value="#{moveBean.destinationListIndex}" size="1" onchange="javascript:submit();" rendered="#{moveBean.sourceListIndex != null}">
    <f:selectItems value="#{moveBean.destinationLists}" />
</h:selectOneListbox>                                The second list is correctly only ever displayed when the first one has been selected.
However, the value of the second list ("#{moveBean.destinationListIndex}") is never applied.
Given that this is essentially a request mode operation, I'm loathe to make it into a session bean, but I'm not faced with too many options.
Help!
Suggestions?
-Chris

Answer 1

You have four options:
1) Make it a session bean.I did half of this. It was the value of the selects that I moved to a session object and kept the getting of the values of the list boxes to a request scope.
<h:selectOneListbox styleClass="selectOneListbox" value="#{sessionObject.sourceListIndex}" size="1" onchange="javascript:submit();">
    <f:selectItems value="#{databaseBean.sourceLists}" />
</h:selectOneListbox>The databaseBean is the request scoped object. This has worked for me in this instance.
2) Put the data to be stored in session in
context.getExternalContext().getSesisonMap().
3) Put the data to be transferred from page to page
in h:inputHidden.
4) Use componentbindings.How would this solve the problem? An example, please.