This content has been marked as final.
Show 2 replies
-
1. Re: Blocking concurrent calls
lvdberg Aug 20, 2010 6:00 PM (in response to yasudevil)Hi,
You can use the s:defaultaction tag inside the button, This makes the login button trigger whenever you hit the enter. The second part is disabling the button while its processing. This can be solved by using a small modalpanel when the system is processing-
<a4j:commandButton id="restoreButton" image="../images/16/Redo.png" action="#{bean.doSomething" reRender="growl,resultTable, pagingPanel " eventsQueue="inputQueue" limitToList="true" ignoreDupResponses="true" requestDelay="500" onclick="#{rich:component('waitPanel')}.show();" oncomplete="#{rich:component('waitPanel')}.hide();" />
And the waitpanel:
<h:form id="waitForm" > <rich:modalPanel id="waitPanel" autosized="true" domElementAttachment="form" > <h:graphicImage value="/images/wait30.gif" /> </rich:modalPanel> </h:form>
Hopefully this helps,
Leo
-
2. Re: Blocking concurrent calls
yasudevil Aug 23, 2010 2:24 PM (in response to yasudevil)Thanks for the reply, it really helped me with another thing but this bug that I'm having is related to this one. I was mistaken saying it was caused by concurrent calls actually the problem was another.
http://seamframework.org/Community/SeamTokenTagProblemCSRF
The link above has a fix for the issue that I'm facing right now. There is a code to fix the clientUIDGenerator, after implementing that my form started to work normally.