[JBoss JIRA] (ARQGRA-190) Support initializing Page Objects declared with generic types
by Juraj Húska (JIRA)
Juraj Húska created ARQGRA-190:
----------------------------------
Summary: Support initializing Page Objects declared with generic types
Key: ARQGRA-190
URL: https://issues.jboss.org/browse/ARQGRA-190
Project: Arquillian Graphene
Issue Type: Feature Request
Components: core
Affects Versions: 2.0.0.Alpha2
Reporter: Juraj Húska
Assignee: Juraj Húska
When using @Page annotation to initialize Page Object in this way:
{code}
public abstract class AbstractWebDriverTest<P extends AbstractPage> extends Arquillian {
@Page
public P page;
}
{code}
I am getting this:
{code}
java.lang.RuntimeException: Can not initialise Page Object!
at org.jboss.arquillian.graphene.enricher.ComponentObjectsEnricher.initializePageObjectFields(ComponentObjectsEnricher.java:106)
at org.jboss.arquillian.graphene.enricher.ComponentObjectsEnricher.enrich(ComponentObjectsEnricher.java:64)
at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
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.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:113)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
{code}
It is caused with this line in PageFragmentEnricher:
{code}
Class declaredClass = Class.forName(i.getGenericType().toString().split(" ")[1]);
{code}
I need support for Page Objects declared with generic type.
--
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
[JBoss JIRA] (ARQ-997) Provide Arquillian Core functionality as OSGi Bundle
by Thomas Diesler (JIRA)
Thomas Diesler created ARQ-997:
----------------------------------
Summary: Provide Arquillian Core functionality as OSGi Bundle
Key: ARQ-997
URL: https://issues.jboss.org/browse/ARQ-997
Project: Arquillian
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Base Implementation, OSGi Containers
Reporter: Thomas Diesler
Assignee: Thomas Diesler
(10:06:40 AM) tdiesler: mgoldmann, lets talk about the individual sub task. Embedded ARQ Core functionality for example. Instead of embedding the jars arq-osgi could include the *.class files. I suppose that is equally unacceptable, right?
(10:07:22 AM) akurtakov: tdiesler: if they are not built from source yes
(10:07:27 AM) mgoldmann: yes, classes are unpcettable too, you can embed what you just build (arq-osgi jars)
(10:08:19 AM) tdiesler: mgoldmann, but arq core was build by some other process - noi?
(10:08:53 AM) mgoldmann: yes, so we cannot embed it
(10:09:13 AM) mgoldmann: but we can bundle arq-core in a jar at the time of building arq-core
(10:09:15 AM) tdiesler: mgoldmann, that process could make an aggregated bundle that arq-osgi could use (i.e. import packages from)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (ARQ-982) Response header size exceeded in Warp tests.
by Jakub Narloch (JIRA)
Jakub Narloch created ARQ-982:
---------------------------------
Summary: Response header size exceeded in Warp tests.
Key: ARQ-982
URL: https://issues.jboss.org/browse/ARQ-982
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Environment: JBoss AS 7.1.1
Reporter: Jakub Narloch
This can be reproduced in remote JBoss AS 7 by moving in PhaserBasicTest(phaser-ftest module) the {code}@ArquillianResource URL contextPath;{code} into the ServerAssertion. This ends in exceeding the maximum size of the response header:
{code}
16:55:05,703 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http--127.0.0.
1-8080-1) An exception or error occurred in the container during the request processing: java.lang.ArrayIndexOutOfBoundsException: 8192
at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.java:698) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.java:607) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.InternalOutputBuffer.sendHeader(InternalOutputBuffer.java:479) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1648) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:998) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.Response.action(Response.java:190) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.Response.sendHeaders(Response.java:390) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:335) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:301) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.Response.finishResponse(Response.java:479) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:395) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb 7.0.13.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months