[
https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin...
]
Bernard Labno edited comment on ARQGRA-274 at 4/26/13 7:21 PM:
---------------------------------------------------------------
I've manually included interception and guard javascripts invoked ...
and it looks like invoking fast several events that trigger ajax (i.e. typing fast and
having ajax on keyup - sendKeys) will block sending further requests.
That's why commenting try/catch block from previous post made test pass - there was no
fast ajax event.
Ajax requests are getting into queue (jsf.js) but the queu is not getting dequeued (and it
should be on onComplete aka onreadystatechange).
was (Author: blabno):
I've manually included interception and guard javascripts invoked ...
and it looks like invoking fast several events that trigger ajax (i.e. typing fast and
having ajax on keyup - sendKeys) will block sending further requests.
That's why commenting try/catch block from previous post made test pass - there was no
fast ajax event.
The request guard does timeout for delayed requests
---------------------------------------------------
Key: ARQGRA-274
URL:
https://issues.jboss.org/browse/ARQGRA-274
Project: Arquillian Graphene
Issue Type: Bug
Affects Versions: 2.0.0.Alpha3
Reporter: Bernard Labno
Assignee: Lukáš Fryč
Fix For: 2.0.0.Alpha4
Original Estimate: 2 hours
Remaining Estimate: 2 hours
In RichFaces, there is request queue which can delay a processing of an user action which
avoids overwhelming communication channel.
This is simply the case where request guard should:
* wait specified timeout (by default type "Ajax" timeout) for user action to
start AJAX request (xhr.open)
* then wait another timeout (by default type "Ajax" timeout) for AJAX action to
complete the request (xhr.readyState == 4)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira