May 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-300) Guard Ajax ends with timeout exception

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-300?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-300: ------------------------------ Original Estimate: 4 hours Remaining Estimate: 4 hours > Guard Ajax ends with timeout exception > -------------------------------------- > > Key: ARQGRA-300 > URL: https://issues.jboss.org/browse/ARQGRA-300 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Sona Jamborova > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When I use guard Ajax, then test ends with exception "Timed out after 7 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory". > If I do not use guards, then this operation takes max. 2 seconds. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1286) Support Warp on Java EE 5 (Servlets 2.5) compliant containers

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1286?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1286: --------------------------------- {code} deployment.webXml(new Function<WebAppDescriptor, WebAppDescriptor>() { public WebAppDescriptor apply(WebAppDescriptor webXml) { webXml .createFilter() .asyncSupported(true) .filterName("WarpFilter") .filterClass(WarpFilter.class.getName()) .up() .createFilterMapping() .filterName("WarpFilter") .urlPattern("/*"); return webXml; }; }); {code} > Support Warp on Java EE 5 (Servlets 2.5) compliant containers > ------------------------------------------------------------- > > Key: ARQ-1286 > URL: https://issues.jboss.org/browse/ARQ-1286 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Warp is currently focused on Java EE 6 and higher, since it uses {{@WebFilter}} annotation to intercept incoming requests. > We may decide to support Servlets 2.5 containers as well in case there is enough interest (please vote if you are interested). -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1290) Warp: support Servlets 2.5

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1290?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1290: --------------------------------- {code} deployment.webXml(new Function<WebAppDescriptor, WebAppDescriptor>() { public WebAppDescriptor apply(WebAppDescriptor webXml) { webXml .createFilter() .asyncSupported(true) .filterName("WarpFilter") .filterClass(WarpFilter.class.getName()) .up() .createFilterMapping() .filterName("WarpFilter") .urlPattern("/*"); return webXml; }; }); {code} > Warp: support Servlets 2.5 > -------------------------- > > Key: ARQ-1290 > URL: https://issues.jboss.org/browse/ARQ-1290 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > > Warp currently uses {{@WebFilter}} and thus it is supported only when using Servlets 3.0 protocol. > Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced. > Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the {{web.xml}} enrichment will be used instead. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1386) Warp: provide a meaningful message when test isn't annotated with @WarpTest

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1386?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1386: ---------------------------- Estimated Difficulty: Low > Warp: provide a meaningful message when test isn't annotated with @WarpTest > --------------------------------------------------------------------------- > > Key: ARQ-1386 > URL: https://issues.jboss.org/browse/ARQ-1386 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > > When the test class isn't annotated, the execution of {{Warp}} will throw {{NullPointerException}}: > https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2... > Provide a meaningful message which will instruct a user to add {{@WarpTest}} annotation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1386) Warp: provide a meaningful message when test isn't annotated with @WarpTest

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1386: ------------------------------- Summary: Warp: provide a meaningful message when test isn't annotated with @WarpTest Key: ARQ-1386 URL: https://issues.jboss.org/browse/ARQ-1386 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha2 Reporter: Lukáš Fryč When the test class isn't annotated, the execution of {{Warp}} will throw {{NullPointerException}}: https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2... Provide a meaningful message which will instruct a user to add {{@WarpTest}} annotation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1385) Drone: resize the PhantomJS window after the start of a test

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1385: ------------------------------- Summary: Drone: resize the PhantomJS window after the start of a test Key: ARQ-1385 URL: https://issues.jboss.org/browse/ARQ-1385 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.0.Alpha2 Reporter: Lukáš Fryč Assignee: Karel Piwko The PhantomJS starts with incredibly small window, so it prevents to run lot of the tests where elements aren't shown in the initial viewport. We can use this instructions selectively for PhantomJS to make it work: https://github.com/richfaces/richfaces5/blob/master/build/build-resources... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-300) Guard Ajax ends with timeout exception

by Sona Jamborova (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-300?page=com.atlassian.jira.plugin... ] Sona Jamborova commented on ARQGRA-300: --------------------------------------- Hi, the application is same as for https://issues.jboss.org/browse/ARQGRA-297. After login, click on Knowledge link and you will see Project Explorer. List in file system invoke AJAX requests. > Guard Ajax ends with timeout exception > -------------------------------------- > > Key: ARQGRA-300 > URL: https://issues.jboss.org/browse/ARQGRA-300 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Sona Jamborova > Assignee: Jan Papousek > Fix For: 2.0.0.Alpha5 > > > When I use guard Ajax, then test ends with exception "Timed out after 7 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory". > If I do not use guards, then this operation takes max. 2 seconds. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1376) Couldn't resolve @ArquillianResource URL with Tomcat 7 Embedded container

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1376?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1376. ------------------------------ Assignee: Aslak Knutsen Resolution: Duplicate Issue > Couldn't resolve @ArquillianResource URL with Tomcat 7 Embedded container > ------------------------------------------------------------------------- > > Key: ARQ-1376 > URL: https://issues.jboss.org/browse/ARQ-1376 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Ubuntu 12.04.2 LTS > Reporter: Anthony O. > Assignee: Aslak Knutsen > Labels: ArquillianResource, URL, tomcat7 > Attachments: test-project.zip > > > I'm trying to test a simple JAX-RS service (resteasy) with Tomcat 7 embedded container, and Arquillian throws me an exception when trying to resolve my {{@ArquillianResource URL}} : > {noformat} > java.lang.RuntimeException: Could not lookup value for field private java.net.URL com.mycompany.myapp.ws.WebServiceTest.deploymentUrl > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:61) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:770) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > Caused by: java.lang.RuntimeException: Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@56bebb88 > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:115) > at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57) > ... 72 more > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1384) Arquiliian Persistence TomEE support

by Tamás Kimmel (JIRA)

Tamás Kimmel created ARQ-1384: --------------------------------- Summary: Arquiliian Persistence TomEE support Key: ARQ-1384 URL: https://issues.jboss.org/browse/ARQ-1384 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha6 Reporter: Tamás Kimmel Assignee: Bartosz Majsak It would be nice to have a TomEE test profile. I've created one. Running test on the modul i got 1 fail, and 2 errors. All others are green. And (hopefully) i did not broke other profiles. Please take a look at it. https://github.com/kumm/arquillian-extension-persistence/commits/tomee -- 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

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ] Jan Papousek updated ARQGRA-274: -------------------------------- Assignee: Lukáš Fryč (was: Jan Papousek) > 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

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2013