- 
        1. Re: 'selected' item of h:selectOneMenu is to updatedilya_shaikovsky Feb 12, 2008 10:38 AM (in response to emsa)seems the same as described http://labs.jboss.com/wiki/RichFacesTwoInputText 
- 
        2. Re: 'selected' item of h:selectOneMenu is to updatedemsa Feb 12, 2008 12:36 PM (in response to emsa)Yes I guess that is related, but if I display the selected value with <h:outputText value="#{node.selected}" /> or similar I always get the correct value. 
 I have however solved the problem at hand, I bit ugly - but working. I walk through the Component Tree finding the affected UISelectOne and doing a setValue() with the correct value.
- 
        3. Re: 'selected' item of h:selectOneMenu is to updatedilya_shaikovsky Feb 13, 2008 4:11 AM (in response to emsa)Of course, outputText doen't updates its value during request.. So this is not a problem.. 
 To your case more prefered solution was surrounding with region component inputs and selects which should be processed alone (with further inputs and selects updates.)
- 
        4. Re: 'selected' item of h:selectOneMenu is to updatedemsa Feb 18, 2008 12:45 PM (in response to emsa)Yes, but the strange thing is that it works with inputTexts as well - it is only the select-menus that contains the stale values. 
- 
        5. Re: 'selected' item of h:selectOneMenu is to updatedemsa Feb 18, 2008 1:01 PM (in response to emsa)One more thing, it is even so that if the selectItems change it is reflected in the options but the selected value is not. 
 Any clues?
- 
        6. Re: 'selected' item of h:selectOneMenu is to updatedilya_shaikovsky Feb 19, 2008 5:20 AM (in response to emsa)could you please share your sample with me? (war with sources and libs preferred.) 
- 
        7. Re: 'selected' item of h:selectOneMenu is to updatedemsa Feb 19, 2008 8:03 AM (in response to emsa)Will do - I have a deadline this week so it will have to wait until next week. But as far as I can understand from behavior and code is that once a value is submitted to the control no value will be read from from the backing bean. It does not mater if I surround different controls in a4j:regions or not. My solution, for now, is to navigate to make sure a fresh tree is created. 
 
    