I have an ace:autoCompleteEntry component configured as follows:

                <ace:autoCompleteEntry id="meCode1"
                        textChangeListener="#{crListDataTableBean1.getMeCodeAcTxtChng}"
                        valueChangeListener="#{crListDataTableBean1.getMeCode1AcList}"
                        listValue="#{crListDataTableBean1.meCodeAutoCompleteList}"
                        listVar="me" rows="10"
                        value="#{crListDataTableBean1.formData.meCode1}"
                        filterBy="#{me.stringKey}" filterMatchMode="none">
                        <f:facet name="row">
                            <h:panelGrid columns="2">
                                <h:outputText value="#{me.stringKey}" />
                                <h:outputText value="#{me.desc}" />
                            </h:panelGrid>
                        </f:facet>
                        <f:attribute name="SOURCE" value="test"/>
                        <f:validator validatorId="test.validator" />
                        <ace:ajax render="@form" event="submit"/>
                        <ace:ajax render="@form" event="blur"/>
                </ace:autoCompleteEntry>

When I enter text and tab out, I see the textChangeListener executed twice. In general, there appear to be 3 submits to the server instead of the expected 2. This could be resulting in the Validator message being cleared when you expect to see it.

Also, when this component is placed in an ace:dataTable with an ace:autoCompleteEntry component in the adjacent column, there are some observations seen related to focus:

- If type in field, select an entry from the drop-down, move to the next autoCompleteEntry field, type ‘0’ and the 0 appears on the end of the previous column field. The focus appears to be going back to the non-previous field after selecting a valid code.

I have attached a Test application with ace:autoCompleteEntry tags in adjacent columns of an ace:dataTable.