Command buttons trigger second press actions (jsf)

Question

I came to the strange behavior of my application. Command buttons begin to trigger actions on the second hit. At first, nothing happens. It works on firefox and chromium, but in epiphany it works as usual.

My environment: - ubuntu 11.04 - glass fish 3.1.1 - jsf 2.X - primary 3.2 - firefox 12.0 - insight 2.30.6

Code example:

<ui:define name="content"> <h:form id="form"> <h:panelGrid id="panelGrid" columns="3"> <h:outputText value="#{msg.fieUserName}:"/> <h:inputText id="name" value="#{userBb.editedUser.username}" /> <h:message for="name" styleClass="error_msg"/> <h:outputText value="#{msg.fieUserDescription}:"/> <h:inputText id="description" value="#{userBb.editedUser.description}" /> <h:message for="description" styleClass="error_msg"/> <h:outputText value="#{msg.fieUserPassword}:"/> <h:inputSecret id="password" value="#{userBb.editedUser.password}" redisplay="true"/> <h:message for="password" styleClass="error_msg"/> <h:outputText value="#{msg.fieUserRights}:"/> <p:selectOneMenu id= "rights" value= "#{userBb.editedUserGroup}" converter="#{pGroupOfUsersConverter}"> <f:selectItems value ="#{groupDao.findAll()}" var ="row" itemLabel="#{groupDao.rightsDescription(row.id)}" itemValue="#{row.groupname}" > </f:selectItems> </p:selectOneMenu> <h:message for="rights" styleClass="error_msg"/> <h:outputText value="#{msg.fiePorofolioName}:" rendered="#{userBb.chosenNew}"/> <h:inputText id="portName" value="#{userBb.portfelForNewUser.nazwa}" rendered="#{userBb.chosenNew}"> <f:validateBean disabled="true" /> </h:inputText> <h:message for="portName" styleClass="error_msg" rendered="#{userBb.chosenNew}"/> <h:outputText value="#{msg.fiePotofolioCurrency}:" rendered="#{userBb.chosenNew}"/> <p:selectOneMenu id= "waldep" value= "#{userBb.portfelForNewUser.walutaDepozytowa}" converter="#{igConverter}" rendered= "#{userBb.chosenNew}" > <f:selectItems value= "#{igDao.waluty}" var= "row" itemLabel="#{row.nazwa}"/> </p:selectOneMenu> <h:message for="waldep" styleClass="error_msg" rendered="#{userBb.chosenNew}"/> </h:panelGrid> <h:panelGrid columns="2"> <h:commandButton value="#{msg.butCreate}" action="#{userBb.formCreate()}" rendered="#{userBb.chosenNew}" /> <h:commandButton value="#{msg.butSave}" action="#{userBb.formEdit()}" rendered="#{!userBb.chosenNew}"/> <h:commandButton value="#{msg.butBack}" action="#{userBb.formBack()}"/> </h:panelGrid> </h:form> </ui:define> 

In this example, the userBb.formCreate () method is called only the second time you click on the command button, although the button is visible. When the fields are not filled out properly, and the corresponding messages appear next to them, but ... only with the second press! Any tips?

I check points from: this tip , but haven't found a solution.

Answer 1

Well, I found that not so. So:

Appearance of the problem: I have a page for user data. Some input elements and command buttons. When you click the Create button, the input data is entered. If the data is in order, the user is created and the user table appears or when errors appear, error messages appear and the user remains on one page:

I found some erratic behavior. Nothing happened on the first click (action), the effect is only the second and subsequent actions. But. This behavior Applied to the web browser used.

All actions are performed from the first click, in web browsers: epiphany and konqueror. Although in firefox and chromium I have observed this erratic behavior, which I described above. Code for command button:

 <h:commandButton value="#{msg.butCreate}" action="#{userBb.formCreate()}" rendered="#{userBb.chosenNew}"/> 

Different types of behavior in different web browsers.

Cause. The reason was given by @Balusc in his post , which I read about the first time. It was really pt. 7.

Decision. I tried changing the button declaration as follows:

 <h:commandButton value="#{msg.butCreate}" action="#{userBb.formCreate()}" rendered="#{userBb.chosenNew}"> <f:ajax render="userForm"/> </h:commandButton> 

where userForm was the correct identifier for h: form. There is no result, yet only the second and subsequent clicks have an effect - error messages are displayed.

So, I changed the ad command command from the previous page, which called up the page with erratic behavior. Originally it was:

 <p:commandButton value="#{msg.butNew}" action="#{userBb.actionNew()}"/> 

command line button. And that was the way Balusk wrote: "If the parent with the UICommand button was visualized / updated using an ajax request in advance , then the first action will always fail."

So, I changed the declaration to:

 <p:commandButton value="#{msg.butNew}" action="#{userBb.actionNew()}" ajax="false"/> 

What is it. It works great in any browser for the first action.