February 2012 - arquillian-issues

[JBoss JIRA] (ARQAJO-125) Umbrella: Rename the project to Graphene

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQAJO-125: --------------------------------- Summary: Umbrella: Rename the project to Graphene Key: ARQAJO-125 URL: https://issues.jboss.org/browse/ARQAJO-125 Project: Arquillian Ajocado Issue Type: Feature Request Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.CR3 -- 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

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (ARQAJO-121) Split arquillian-testng/junit to support -standalone and -container version

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQAJO-121: --------------------------------- Summary: Split arquillian-testng/junit to support -standalone and -container version Key: ARQAJO-121 URL: https://issues.jboss.org/browse/ARQAJO-121 Project: Arquillian Ajocado Issue Type: Enhancement Components: integration Affects Versions: 1.0.0.CR2 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.CR3 Now it's not possible to use ajocado with {{arquillian-junit-standalone}}. In order to support it, {{arquillian-ajocado-junit}} should be renamed to {{arquillian-ajocado-junit-container}} and new depchain {{arquillian-ajocado-junit-container}} should be created. -- 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

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] (ARQAJO-122) Class Point should override default equals and hashCode

by Juraj Huska (JIRA)

Juraj Huska created ARQAJO-122: ---------------------------------- Summary: Class Point should override default equals and hashCode Key: ARQAJO-122 URL: https://issues.jboss.org/browse/ARQAJO-122 Project: Arquillian Ajocado Issue Type: Enhancement Components: core Affects Versions: 1.0.0.CR2 Reporter: Juraj Huska Priority: Minor org.jboss.arquillian.ajocado.geometry.Point should override default equals and hashCode, since now the following statement does not return what expected, that these two points should be equal: {code} Point point1 = new Point(20, 20); Point point2 = new Point(20, 20); point1.equals(point2); {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

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-502) Support arquillian.xml configuration in Maven Plugin

by Aslak Knutsen (JIRA)

Support arquillian.xml configuration in Maven Plugin ---------------------------------------------------- Key: ARQ-502 URL: https://issues.jboss.org/browse/ARQ-502 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation, Maven Plugin Reporter: Aslak Knutsen Maven Plugin should support configuration of Containers either via a arquillianXml file location property, or inline xml. {code:xml} <configuration> <arquillianXml>some/path/arq.xml</arquillianXml> <config> <container qualifer="name"> <configuration> <property name="jbossHome">/home</property> </configuration> </container> </config> </configuration> {code} (arquillianXml property require File Path support in Core, currently only ClassPath resources. config-impl-base:ConfigurationRegistrar) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] (ARQ-708) Should support keeping container alive between execution phases

by Aslak Knutsen (Created) (JIRA)

Should support keeping container alive between execution phases --------------------------------------------------------------- Key: ARQ-708 URL: https://issues.jboss.org/browse/ARQ-708 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Maven Plugin Affects Versions: maven_1.0.0.Alpha1 Reporter: Aslak Knutsen Fix For: maven_1.0.0.next The Arquillian Maven plugin should be able to be configured to run different commands in different execution phases. e.g. before integration -> start container ---- do other plugin stuff here after integration -> stop container -- 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

12 years, 3 months

4
5
0 / 0

[JBoss JIRA] (ARQ-775) ARQ produces messed up log with one character per line in AS7 testsuite

by Radoslav Husar (JIRA)

Radoslav Husar created ARQ-775: ---------------------------------- Summary: ARQ produces messed up log with one character per line in AS7 testsuite Key: ARQ-775 URL: https://issues.jboss.org/browse/ARQ-775 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Radoslav Husar Looks like ONLY arquillian logging is messed up thus putting it here. Log looks like this, snip: {noformat} 14:18:32,799 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-3-thread-1) ISPN000082: Stopping the RpcDispatcher 14:18:33,113 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.lifecycle.cluster] (Incoming-7,null) JBAS010247: New cluster view for partition cluster (id: 2, delta: -1, merge: false) : [node-udp-0/cluster] 14:18:33,114 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-7,null) ISPN000094: Received new cluster view: [node-udp-0/cluster|2] [node-udp-0/cluster] 14:18:33,389 INFO [org.jboss.as.repository] (management-handler-threads - 1) JBAS014901: Content removed from location /home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-1/standalone/data/content/61/d2eac7ab6bf21961f39a0f152c6459f3c17aab/content 14:18:33,389 INFO [org.jboss.as.server] (management-handler-threads - 1) JBAS018558: Undeployed "singleton.war" 1 4 : 1 8 : 4 3 , 3 9 2 I N F O [ o r g . j b o s s . a r q u i l l i a n . c o n t a i n e r . t e s t . i m p l . c l i e n t . c o n t a i n e r . C l i e n t C o n t a i n e r C o n t r o l l e r ] ( m a i n ) M a n u a l s t o p p i n g o f a s e r v e r i n s t a n c e URLs are: http://127.0.0.1:8080/singleton/singleton/service, http://127.0.0.1:8180/singleton/singleton/service 14:18:44,777 INFO [stdout] (MSC service thread 1-2) Service controller state is UP, waiting for transition to REMOVED 14:18:44,779 INFO [stdout] (MSC service thread 1-2) Service controller state is STOPPING, waiting for transition to REMOVED 14:18:44,787 INFO [org.jboss.as.clustering.infinispan] (pool-12-thread-1) JBAS010282: Stopped default cache from cluster container 14:18:44,807 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment singleton.war in 51ms 14:18:44,848 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-3-thread-1) ISPN000082: Stopping the RpcDispatcher 14:18:45,181 INFO [org.jboss.as.repository] (management-handler-threads - 4) JBAS014901: Content removed from location /home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/data/content/29/2267739197896e484c0ff0fa35731be4d18c0d/content 14:18:45,182 INFO [org.jboss.as.server] (management-handler-threads - 4) JBAS018558: Undeployed "singleton.war" 1 4 : 1 8 : 4 5 , 1 8 4 I N F O [ o r g . j b o s s . a r q u i l l i a n . c o n t a i n e r . t e s t . i m p l . c l i e n t . c o n t a i n e r . C l i e n t C o n t a i n e r C o n t r o l l e r ] ( m a i n ) M a n u a l s t o p p i n g o f a s e r v e r i n s t a n c e {noformat} -- 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

12 years, 3 months

4
19
0 / 0

[JBoss JIRA] Created: (ARQ-453) Implement Apache Httpd managed container

by Ondrej Zizka (JIRA)

Implement Apache Httpd managed container ---------------------------------------- Key: ARQ-453 URL: https://issues.jboss.org/browse/ARQ-453 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ondrej Zizka (15:22:04) OndrejZizka: Would it make sense to create httpd container, to make it manageable? (15:22:25) OndrejZizka: Ommiting the deploy stuff (15:37:40) aslak: OndraZizka, what's the purpose ? (15:38:47) OndrejZizka: I'd make use of it for EWS testing. (15:38:59) OndrejZizka: So I would have everything under one roof (15:39:41) OndrejZizka: But right, I could use other Java httpd management lib if there's any (15:41:39) aslak: OndraZizka, what do you do with it without deploy? (15:55:37) aslak: OndraZizka, it could be useful (16:02:21) OndrejZizka: aslak: I would configure httpd, restart it, and test something from a client side from junit (16:03:21) OndrejZizka: Right, I would assume that something is already "deployed" (16:03:47) OndrejZizka: I don't know how we could embrace the "deploy" concept for httpd (16:04:22) OndrejZizka: Perhaps just by copying it to some dir detected in httpd.conf, e.g. DocumentRoot and extracting -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] (ARQ-761) Document extension in confluence.

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-761: ---------------------------------- Summary: Document extension in confluence. Key: ARQ-761 URL: https://issues.jboss.org/browse/ARQ-761 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Seam2 Affects Versions: seam2_1.0.0.Alpha1 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: seam2_1.0.0.next -- 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

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-184) NPE in o.j.aop.Dispatcher.invoke:117 - ARQ Alpha2 + remote-50 + as-client 5.0.1

by Ondrej Žižka (JIRA)

NPE in o.j.aop.Dispatcher.invoke:117 - ARQ Alpha2 + remote-50 + as-client 5.0.1 ------------------------------------------------------------------------------- Key: ARQ-184 URL: https://jira.jboss.org/browse/ARQ-184 Project: Arquillian Issue Type: Bug Environment: ARQ Alpha2 + remote-50 + as-client 5.0.1 + EAP 5.0.1 Reporter: Ondrej Žižka STR: 1) Download the project attached, 2) Run EAP 5.0.1 default, but I think the request doesn't even get sent. 3) mvn clean install (profile is self-enabled), 4) You'll get a NPE: org.jboss.arquillian.impl.event.FiredEventException: org.jboss.arquillian.spi.LifecycleException: Could not connect to container at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:71) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: org.jboss.arquillian.spi.LifecycleException: Could not connect to container at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:89) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 24 more Caused by: java.lang.NullPointerException at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:117) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:210) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:768) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:721) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:206) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at AOPProxy$1.loadProfile(AOPProxy$1.java) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.initDeploymentManager(JBossASRemoteContainer.java:222) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:85) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:71) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at AOPProxy$1.loadProfile(AOPProxy$1.java) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.initDeploymentManager(JBossASRemoteContainer.java:222) at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:85) ... 27 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
12
0 / 0

[JBoss JIRA] Created: (ARQ-131) Include utility base class to simplify JPA testing

by Paul Bakker (JIRA)

Include utility base class to simplify JPA testing -------------------------------------------------- Key: ARQ-131 URL: https://jira.jboss.org/jira/browse/ARQ-131 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Reporter: Paul Bakker Priority: Minor Two things are often needed when testing JPA code: -1 Counting rows in a table -2 Rolling back the transaction after each test (to speed up test execution, while potentially dangerous) To simplify testing it would be good to have a set of base classes that implement this common functionality. Test class can extend a base class when this kind of functionality is required. The Spring framework has excellent support for this and can be used for inspiration: http://static.springsource.org/spring/docs/3.0.x/spring-framework-referen... I included some example code that I wrote myself to get a feel how difficult it would be to implement. The code uses an embedded container using the EJB 3.1 API, but should off course integrate with Arquillian. By default each testcase runs in a transaction (using the usertransaction) and is rolled back at the end of the test, unless the testcase is annotated @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED). The rollback behavior can be changed with the custom @RollbackAfterTest anotation. I would be happy to help implementing this feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012