BUG - JSF InputText boxes not populating properly

Question

Okay,
Here's the situation:
I have an edit page (JSF Web) that allows the user to pick an item to edit from a SelectOneMenu tag. When they pick the item the page rerenders and shows the object associated with the selected item allowing the user to edit the object in various InputText controls.
First of all the ValueChangeListener event doesn't work for the SelectOneMenu tag - the event is not recognized in the backing bean (with or without immediate set, the event code is never accessed.) - and so I had to tie the change to the pressing of a command button.
Upon pressing the command button, in the action event, I find the object from the selected item. Now I want to set the input text boxes in the screen to the various values of the object. There are two ways to do this. I either set the value property of the bound (using the binding property) backing bean to the objects property - the code looks like this:
<h:inputText binding="#{EditCalendarBean.name}"
value="#{EditCalendarBean.name.value}"/>
This results in a fatal error that halts the OC4J.
Alternatively; I added various properties to the backing bean one for each property of the object and bound the object's properties to these and then bound the user interface's value properties to the bean properties. For example, imagine a user interface control InputText tag called "name" has it's value property bound to a property on the bean called Name which returns String. This configuration runs but the InputText control when the page is re-rendered (after the submit), is empty even though I've set the value property. However, if I add an OutputText control to the page and bind it's value property to the same String property of the bean, the outputText control correctly shows the value of the object.
The code looks like this:
<!-- code in the page -->
<h:inputText id="name" binding="#{EditCalendarBean.name}"
value="#{EditCalendarBean.nameValue}"/>
// Code in the Backing bean:
// Find the Bean from the submitted id from the SelectMenuTag.
CalendarData data = manager.getCalendarById(calendarID) ;
// Set value of the UITextInput components on the page.
this.getName().setValue(data.getName());
this.getDescription().setValue(this.getDescription());
// This results in a fatal error that halts the OC4J
// Method 2: declare two String properties on the bean and set them
// Then, in the page use the Value property of the InputText control.
// This runs but doesn't populate the controls. It does populate them if
// the contols are OutputText controls though!!!
this.setNameValue(data.getName());
this.setDescriptionValue(data.getDescription());
Best regards,
Nigel

Answer 1

Yes - this really is a bug. Any changes to make to the selectItems tag through the properties dialog rewrites the tag source code to seperate the selectOne tag and the selectItems tag. For example, before you use the dialog, you tag code could look like this:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1">
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
</h:selectOneMenu>
After the use of the dialog the code will be rewritten as:
<h:selectOneMenu binding="#{backing_showFactory.selectOneMenu1}"
id="selectOneMenu1"/>
<f:selectItems value="#{backing_showFactory.allFactories}"
binding="#{backing_showFactory.selectItems2}"
id="selectItems2"/>
Notice, the tags are now seperated instead of the selectItems tag being encased in the selectOneMenu tag.