[JBoss JIRA] (ARQGRA-295) Provide more convenient way for Interceptors registration/unregistration
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-295?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-295:
------------------------------
Fix Version/s: 2.0.0.Alpha5
> Provide more convenient way for Interceptors registration/unregistration
> -------------------------------------------------------------------------
>
> Key: ARQGRA-295
> URL: https://issues.jboss.org/browse/ARQGRA-295
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: api, core
> Affects Versions: 2.0.0.Alpha4
> Reporter: Juraj Húska
> Priority: Minor
> Fix For: 2.0.0.Alpha5
>
>
> It would be nice to have a more simple way of registering/unregistering Interceptors.
> Currently this is supported:
> {code}
> GrapheneProxyInstance proxy = (GrapheneProxyInstance) webdriver;
> proxy.registerInterceptor(new SearchContextInterceptor());
> {code}
> It would be nice to have something like:
> {code}
> Graphene.registerInterceptor(new SearchContextInterceptor());
> {code}
> It will be also good to choose class and method which will be intercepted.
--
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
12 years, 11 months
[JBoss JIRA] (ARQGRA-295) Provide more convenient way for Interceptors registration/unregistration
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-295?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-295:
------------------------------
Fix Version/s: 2.0.0.Alpha6
(was: 2.0.0.Alpha5)
> Provide more convenient way for Interceptors registration/unregistration
> -------------------------------------------------------------------------
>
> Key: ARQGRA-295
> URL: https://issues.jboss.org/browse/ARQGRA-295
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: api, core
> Affects Versions: 2.0.0.Alpha4
> Reporter: Juraj Húska
> Priority: Minor
> Fix For: 2.0.0.Alpha6
>
>
> It would be nice to have a more simple way of registering/unregistering Interceptors.
> Currently this is supported:
> {code}
> GrapheneProxyInstance proxy = (GrapheneProxyInstance) webdriver;
> proxy.registerInterceptor(new SearchContextInterceptor());
> {code}
> It would be nice to have something like:
> {code}
> Graphene.registerInterceptor(new SearchContextInterceptor());
> {code}
> It will be also good to choose class and method which will be intercepted.
--
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
12 years, 11 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č updated ARQGRA-280:
------------------------------
Summary: Refactor handling of staleness to improve performance (was: refactor handling of staleness)
> 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.Alpha5
>
> 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
12 years, 11 months