Bug of JSF spec?

Question

I am not good at English. But but... please hear my JSF Problem.
<h:form>
    <h:inputText id="input1" required="#{true}"/>
    <h:message for="input1"/>
    <h:inputText id="input2" value="#{testBean.value}">
        <f:convertNumber integerOnly="true"/>
    </h:inputText>
    <h:message for="input2"/>
    <h:commandButton/>
</h:form>From browser:
1.Input empty string at input1. (this cause validation error.)
2.Input empty string at input2. (convet to null.)
3.Click commandButton.
I hope:
Display value at input2 is empty string. (My input value is keeped.)
But result is:
Display value at input2 is "#{testBean.value}". (My input value is forgotten...)
In my research:
1.converter converts empty string to null.
2."local value" is set to null.
3.Go to Rnder Response Phase By Input1 validation error.
4.getValue ignore "local value" if it is null and see VE.
Uhh... Why getValue method doesn't see isLocalValueSet?
I can't understand... Please Help me...

Answer 1

Unfortunately I've had no luck with this solution. In my case I am performing a search using a session scope bean. My results are listed in a dataTable and I have an actionListener on a request scoped bean. All of that works fine.
faces-config.xml
<managed-bean>
     <managed-bean-name>searchBean</managed-bean-name>
     <managed-bean-class>com.package.SearchBean</managed-bean-class>
     <managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
     <managed-bean-name>detailBean</managed-bean-name>
     <managed-bean-class>com.package.DetailBean</managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
</managed-bean>
public class DetailBean
     private String field1;
     private String field2;
     //Bind the dataTable component to the controller
     protected transient UIData dataTable;
     //The object used to populate the row in the table that was selected
     protected transient Object row;
     public DetailBean()
          super();
          FacesContext facesContext = FacesContext.getCurrentInstance();
          Boolean isPostback = facesContext.getRenderKit().getResponseStateManager().isPostback(facesContext);
          if(!isPostback) //always seems to be true
               if(dataTable != null)
                    row = dataTable.getRowData();
     public void detail(ActionEvent event)
          row = dataTable.getRowData();
          if(row != null)
               Map<String,String> record = (Map<String,String>)row;
               setField1(record.get("field1"));
               setField2(record.get("field2"));
     public String edit()
          //do the edit
          return "success";
<h:inputText id="field1" value="#{detailBean.field1}" required="true"/>
<h:inputText id="field2Input" value="#{detailBean.field2}"/>
<h:outputText id="field2Text" value="#{detailBean.field2}"/>
<h:inputText id="field2Hidden" value="#{detailBean.field2}"/>
<h:commandLink id="edit" action="#{detailBean.edit}" value="edit"/>
<h:messages errorStyle="color:red" showSummary="true"/>     The values from the table are successfully populated and the page is shown with the values:
field1=test1
field2Input=test2
field2Text=test2
field2Hidden=test2when I clear field1 (required) and submit I have the following:
field1=
field2Input=test2
field2Text=
field2Hidden=test2
message about field1 being requiredI would expect field2Text to still retain the value.
Furthermore if I set the field2Text to readonly="true", it, too, does not retain its value. However in both cases once the required field has a value and is submitted, all values show as expected.
My only workaround for this is to set my detailBean session scope, but that avoids the problem.