-
1. Re: The problem with quick clicks.
sergeysmirnov Apr 9, 2008 11:13 AM (in response to gkuzmin)show the code snippet of the page
-
2. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 11:26 AM (in response to 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. -
3. Re: The problem with quick clicks.
sergeysmirnov Apr 9, 2008 12:32 PM (in response to gkuzmin)the code that contains the active form elements.
Yes, the problem not with the target, but with source of the request. -
4. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 1:01 PM (in response to 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"/>
-
5. Re: The problem with quick clicks.
sergeysmirnov Apr 9, 2008 1:06 PM (in response to gkuzmin)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 -
6. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 1:11 PM (in response to 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 :)
-
7. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 3:05 PM (in response to 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'. -
8. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 3:11 PM (in response to gkuzmin)In the normal work users don't click so quckly, but samebody always make so in the most unsuitable moment :)
-
9. Re: The problem with quick clicks.
sergeysmirnov Apr 9, 2008 3:18 PM (in response to gkuzmin)what else /#{bean.selectedPage}.xhtml page has?
-
10. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 3:34 PM (in response to 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 -
11. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 3:39 PM (in response to 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 -
12. Re: The problem with quick clicks.
sergeysmirnov Apr 9, 2008 3:44 PM (in response to gkuzmin)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.
-
13. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 4:09 PM (in response to gkuzmin)Were es possible, I did es :(
-
14. Re: The problem with quick clicks.
gkuzmin Apr 9, 2008 4:12 PM (in response to gkuzmin)Thank you very mach. I try to solve the problem myself.