[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-274:
------------------------------
Sprint: Sprint for Alpha4, Sprint 1 (was: Sprint for Alpha4)
> 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.Alpha5
>
> 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
11 years, 8 months
[JBoss JIRA] (ARQGRA-224) Page Fragments implementing WebElement delegate interface invocations to Root
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-224?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-224:
------------------------------
Sprint: Sprint for Alpha4, Sprint 1 (was: Sprint for Alpha4)
> Page Fragments implementing WebElement delegate interface invocations to Root
> -----------------------------------------------------------------------------
>
> Key: ARQGRA-224
> URL: https://issues.jboss.org/browse/ARQGRA-224
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Reporter: Lukáš Fryč
> Assignee: Juraj Húska
> Priority: Minor
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> {code:java}
> public abstract static class InputWithPlaceholder implements WebElement {
>
> @Root
> private WebElement input;
>
> public String getText() {
> return input.getAttribute("value");
> }
>
> public Color getTextColor() {
> return ColorUtils.convertToAWTColor(input.getCssValue("color"));
> }
>
> public String getStyleClass() {
> return input.getAttribute("class");
> }
> }
> {code}
--
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
11 years, 8 months
[JBoss JIRA] (ARQGRA-280) Refactor handling of staleness to improve performance
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ]
Jan Papousek commented on ARQGRA-280:
-------------------------------------
In case of invalidation:
{code}
future.getTarget(false)
{code}
otherwise
{code}
future.getTarget(true)
{code}
> Refactor handling of staleness to improve performance
> -----------------------------------------------------
>
> Key: ARQGRA-280
> URL: https://issues.jboss.org/browse/ARQGRA-280
> Project: Arquillian Graphene
> Issue Type: Task
> Affects Versions: 2.0.0.Alpha3
> Reporter: Jan Papousek
> Assignee: Jan Papousek
> Fix For: 2.0.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The current situation of handling staleness is it works purely accidentally in some cases and it prevents any caching of web elements.
> Imagine the following code:
> {code}
> Action action = new Actions(driver).moveToElement(element).build();
> ... // some action causing staleness
> action.perform();
> {code}
> The previous code doesn't throw StaleElementReferenceException only in the case when the action causing staleness finishes before the requested action starts performing and when there is no caching of web elements. Currently Graphene can't force the action to perform again when StaleElementReferenceException is thrown.
> In the case of caching the scenerio would be:
> # element is loaded and put to the cache
> # ... some actions ...
> # action causing staleness is performed
> # the requested action starts performing
> -- cached element is used => StaleElementReferenceException
--
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
11 years, 8 months
[JBoss JIRA] (ARQGRA-280) Refactor handling of staleness to improve performance
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-280:
-----------------------------------
How would you solve a problem of cache invalidation in case of stale reference?
> Refactor handling of staleness to improve performance
> -----------------------------------------------------
>
> Key: ARQGRA-280
> URL: https://issues.jboss.org/browse/ARQGRA-280
> Project: Arquillian Graphene
> Issue Type: Task
> Affects Versions: 2.0.0.Alpha3
> Reporter: Jan Papousek
> Assignee: Jan Papousek
> Fix For: 2.0.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The current situation of handling staleness is it works purely accidentally in some cases and it prevents any caching of web elements.
> Imagine the following code:
> {code}
> Action action = new Actions(driver).moveToElement(element).build();
> ... // some action causing staleness
> action.perform();
> {code}
> The previous code doesn't throw StaleElementReferenceException only in the case when the action causing staleness finishes before the requested action starts performing and when there is no caching of web elements. Currently Graphene can't force the action to perform again when StaleElementReferenceException is thrown.
> In the case of caching the scenerio would be:
> # element is loaded and put to the cache
> # ... some actions ...
> # action causing staleness is performed
> # the requested action starts performing
> -- cached element is used => StaleElementReferenceException
--
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
11 years, 8 months