Validation messages disappearing

[lessonz]

I'm new to RichFaces and JSF in general, and I'm still trying to get my legs under me. I'm using 4.0.0.FINAL. I have two inputText fields that each have their own validators. Their messages seem to have really flaky behavior, appearing and disappearing seemingly at random. At times one will appear and not the other. I'm sure I must just be missing something or doing something wrong. Thanks.

<h:panelGrid id="testGrid" class="centered" columns="3"
    columnClasses="oneThird,oneThird,oneThird">
    <h:outputText value="Header 1" class="bold" />
    <h:outputText value="Header 2" class="bold" />
    <h:outputText value="" class="bold" />
    <h:outputText value="Label 1"
        rendered="#{testBean.value1!='value1'}" />
    <h:inputText binding="#{testBean.name}"
        value="#{testBean.name}" id="in1"
        class="inClass" rendered="#{testBean.value1!='value1'}"
        autocomplete="off">
        <a4j:ajax event="keyup" execute="@this"
            render="actionButtons, warningPanel" />
    </h:inputText>
    <rich:message for="in1"
        rendered="#{testBean.value1!='value1'}" />
    <h:outputText value="Label 2"
        rendered="#{testBean.value1!='value2'}" />
    <h:inputText binding="#{testBean.email}"
        value="#{testBean.email}" id="in2"
        class="inClass" rendered="#{testBean.value1!='value2'}"
        autocomplete="off">
        <a4j:ajax event="keyup" execute="@this"
            render="actionButtons, warningPanel" />
    </h:inputText>
    <rich:message for="in2"
        rendered="#{testBean.value1!='value2'}" />
</h:panelGrid>

[zelenka]

I think it's related to rendered attributes of rich:message

[lessonz]

So, if I put the messages into a container with rendered attributes, would that work?    

[lessonz]

I tried putting the rich messages inside of a4j:outputPanels and moving the rendered attributes to those but no change. Any other ideas?

[ilya_shaikovsky]

as both messages are auto-updateable and both your inputs submitted separately (execute="@this") - that's expected behavior. (once one fail - both messages are update automatically and only one containes errors as second input not processed). in order to avoid - add limitRender=true to each a4j:ajax and point render to corresponding message id instead.

[lessonz]

Thanks Ilya, that got it sorted.