May 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-304) The interceptor for handling StaleElementReferenceException is not present

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-304?page=com.atlassian.jira.plugin... ] Jan Papousek reassigned ARQGRA-304: ----------------------------------- Assignee: Jan Papousek > The interceptor for handling StaleElementReferenceException is not present > -------------------------------------------------------------------------- > > Key: ARQGRA-304 > URL: https://issues.jboss.org/browse/ARQGRA-304 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Assignee: Jan Papousek > Priority: Critical > Fix For: 2.0.0.Alpha5 > > > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... for the stack trace. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-304) The interceptor for handling StaleElementReferenceException is not present

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-304?page=com.atlassian.jira.plugin... ] Lukáš Fryč edited comment on ARQGRA-304 at 5/16/13 5:57 AM: ------------------------------------------------------------ It can be related to the propagation of interceptors though the object tree. I definitely agree with inclusion in Alpha5. was (Author: lfryc): It can be related to the propagation of interceptors though the object tree. > The interceptor for handling StaleElementReferenceException is not present > -------------------------------------------------------------------------- > > Key: ARQGRA-304 > URL: https://issues.jboss.org/browse/ARQGRA-304 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Priority: Critical > Fix For: 2.0.0.Alpha5 > > > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... for the stack trace. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-304) The interceptor for handling StaleElementReferenceException is not present

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-304?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-304: ----------------------------------- It can be related to the propagation of interceptors though the object tree. > The interceptor for handling StaleElementReferenceException is not present > -------------------------------------------------------------------------- > > Key: ARQGRA-304 > URL: https://issues.jboss.org/browse/ARQGRA-304 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Priority: Critical > Fix For: 2.0.0.Alpha5 > > > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... for the stack trace. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-304) The interceptor for handling StaleElementReferenceException is not present

by Jan Papousek (JIRA)

Jan Papousek created ARQGRA-304: ----------------------------------- Summary: The interceptor for handling StaleElementReferenceException is not present Key: ARQGRA-304 URL: https://issues.jboss.org/browse/ARQGRA-304 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.0.0.Alpha4 Reporter: Jan Papousek Priority: Critical See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... for the stack trace. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-304) The interceptor for handling StaleElementReferenceException is not present

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-304?page=com.atlassian.jira.plugin... ] Jan Papousek updated ARQGRA-304: -------------------------------- Fix Version/s: 2.0.0.Alpha5 > The interceptor for handling StaleElementReferenceException is not present > -------------------------------------------------------------------------- > > Key: ARQGRA-304 > URL: https://issues.jboss.org/browse/ARQGRA-304 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Priority: Critical > Fix For: 2.0.0.Alpha5 > > > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... for the stack trace. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1143) Provide support for Groovy 2.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1143?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1143: ---------------------------------- Hi Bartosz, I tried to update the runner to use Groovy 2.1 and Spock 0.7, but for some reason I haven't figured out yet AuxiliaryArchiveAppender is not picking groovy classes into arquillian-spock.jar even if groovy-all is on the classpath no matter of the scope. One of the workarounds I came with was to include groovy-all and 0.7-spock-${groovy-version} fetched by ShrinkWrapMavenResolver based on what groovy/spock version user specifier/transitively depends on in his pom.xml. How does it sound to you? > Provide support for Groovy 2.0 > ------------------------------ > > Key: ARQ-1143 > URL: https://issues.jboss.org/browse/ARQ-1143 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: spock_1.0.0.next > > > This might require changing dependency structure, hence Spock has two different versions as well. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-299) Setup Graphene tests on SauceLabs

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-299?page=com.atlassian.jira.plugin... ] Work on ARQGRA-299 stopped by Jan Papousek. > Setup Graphene tests on SauceLabs > --------------------------------- > > Key: ARQGRA-299 > URL: https://issues.jboss.org/browse/ARQGRA-299 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ] Bernard Labno commented on ARQGRA-274: -------------------------------------- The problem is that a4j:ajax is bound to "keyup" event and calling sendKeys with string longer then single character. If we pass only one character then the guard seems to work. > 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č > Priority: Critical > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1274) @EJB#lookup() support in EJBInjectionEnricher

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1274?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1274: ------------------------------------ Right, that was changed to 3.1 to match what was in the downstream Fedora Repos. > @EJB#lookup() support in EJBInjectionEnricher > --------------------------------------------- > > Key: ARQ-1274 > URL: https://issues.jboss.org/browse/ARQ-1274 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 1.0.4.Final > > > No doubt the {{EJBInjectionEnricher}} deserves a major refactoring (ARQ-77, ARQ-836, ...). However in the mean time we could add {{@EJB#lookup()}} support. The reason is {{EJB#mappedName()}} should not be used in EJB 3.1 (it's product-specific), instead portable JNDI names and {{EJB#lookup()}} should be used. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-301) Support for assertions on errors and console output

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin... ] Lukáš Fryč edited comment on ARQGRA-301 at 5/15/13 6:47 AM: ------------------------------------------------------------ We can enhance the page during a page load - insert a javascript snippet which will register graphene handler. The page can be enhanced using the proxy mechanism (similarly to Warp). was (Author: lfryc): We can enhance the page during a page load - insert a javascript snippet which will register graphene handler. > Support for assertions on errors and console output > --------------------------------------------------- > > Key: ARQGRA-301 > URL: https://issues.jboss.org/browse/ARQGRA-301 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Brian Leathem > > In a recent Graphene based test [\[1\]|https://github.com/richfaces/components/commit/857f73bbf87f495e36c33072c5c4415d4b02be10#L1R85] I registered a window.onerror listener to store errors in the DOM for later retrieval by Graphene/Selenium for use in an assertion. > It would be great if Graphene could do this automatically, providing an API for accessing both error messages, and console output. > [1] https://github.com/richfaces/components/commit/857f73bbf87f495e36... -- 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2013