The problem with quick clicks.

[gkuzmin]

I have a button, which changes strongly the structure of the page (using Ajax request).
If I click this button quickly several times, the application doesn't work anymore. Some references get lost.
It seems, that Richfaces or JSf try to set the old data of the form to the new structure of the component tree.
The components become null values because parametersMap of the request contains data of the old form.
The application works as long as the clicks aren't quick.
Does anyone have the same problem? Is this a bug or did I do something wrong.

[sergeysmirnov]

show the code snippet of the page

[gkuzmin]

The page consist from many templetes and ui:include. What need you execkly?
P. S. With Ajax-request, that don't change the page strongly there isn't the problem.

[sergeysmirnov]

the code that contains the active form elements.
Yes, the problem not with the target, but with source of the request.

[gkuzmin]

Main page :

<f:view>
 <h:form id="mainform">
 <a4j:outputPanel id="panel1">
 <ui:include src="/#{bean.selectedPage}.xhtml"/>
 </a4j:outputPanel>
 </h:form>
</f:view>

include

here there are different input fields ... depends of the current page

<a4j:commandLink reRender="panel1" action="next"/>

[sergeysmirnov]

First of all, define id for the a4j:commandLink explicitly. This is a main source of the problem.

also, if requests flood is an issue for you, read about it at:
http://livedemo.exadel.com/richfaces-demo/richfaces/ajaxAttributes.jsf?c=ajaxattributes

[gkuzmin]

I can certainly to do the link diesable, but i think that have to work without it :) Other work great!!! Thank you for the Richfaces :)

[gkuzmin]

I tried, but that did't helft completlly with Richfaces 3.1.4.
I have tried with 3.20.GA.
the link looks now so:

<a4j:commandLink id="btn_next" reRender="panel1" action="next" eventsQueue="panel1Queue" ignoreDupResponses="true">

It work more stable, but if it is quckly clicked...

[20:38:06.078 [btpool0-13] WARN o.a.m.s.r.html.HtmlRendererUtils - There should always be a submitted value for an input if it is rendered, its form is submitted, and it was not originally rendered disabled or read-only. You cannot submit a form after disabling an input element via javascript. Consider setting read-only to true instead or resetting the disabled value back to false prior to form submission. Component : {Component-Path : [Class: org.ajax4jsf.component.AjaxViewRoot,ViewId: /suretec_voplus/index.jsf][Class: javax.faces.component.html.HtmlForm,Id: mainform][Class: org.ajax4jsf.component.html.HtmlAjaxOutputPanel,Id: wizard][Class: org.ajax4jsf.component.html.HtmlAjaxOutputPanel,Id: gesetzlicheRentenMandant][Class: javax.faces.component.html.HtmlPanelGroup,Id: j_id523][Class: javax.faces.component.html.HtmlInputText,Id: j_id525]}

and javax.el.ELException:
Can't set property 'field1' of type 'int' on class '...' to value 'null'.

[gkuzmin]

In the normal work users don't click so quckly, but samebody always make so in the most unsuitable moment :)

[sergeysmirnov]

what else /#{bean.selectedPage}.xhtml page has?

[gkuzmin]

This is a navigation between simple pages, those have completly different forms. These forms consist of
h:outputText , a4j:outputPanel, h:selectOneMenu and othes from jsf and Richfaces , but only any visual component such as rich:calendar

[gkuzmin]

this is navigation between simple pages,
those consist of h:InputText, h:selectOneMenu, a4j:outputPanel, a4j:jsFunction and other JSF and Richfaces tags but onlu any visual such as rich:Calendar

[sergeysmirnov]

the case becomes complicated. It might be missing something important. If you are able to create a simple test project where the problem is reproducible it will be nice. If so, create an jira issue and attach war to it.

[gkuzmin]

Were es possible, I did es :(

[gkuzmin]

Thank you very mach. I try to solve the problem myself.