April 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-506) Support more complex property types in container configuration

by Gerhard Poul (JIRA)

Support more complex property types in container configuration -------------------------------------------------------------- Key: ARQ-506 URL: https://issues.jboss.org/browse/ARQ-506 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Configuration Reporter: Gerhard Poul Priority: Optional It might sometimes be helpful to support arbitrary property lists within an arquillian configuration, such as when we want to make it possible to pass properties to the underlying container implementations, but that have no effect on the behavior of the arquillian-container-implementation itself. This is not to replace, but to augment the current configuration capability, such that we can provide something like the following in an arquillian.xml: <container qualifier="someQualifier" default="true"> <configuration> <propertyList name="somePropertyName"> <propertyEntry name="somePropertyEntryName" type="java.lang.String" value="someValue" /> <propertyEntry name="somePropertyEntryName2" type="java.lang.Integer" value="1234" /> ... </propertyList> <property name="someOtherProperty">someValue</property> </configuration> </container> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
4
0 / 0

[JBoss JIRA] (ARQ-863) Poor error message when WebArchive deployed with ".jar" name

by Craig Ringer (JIRA)

Craig Ringer created ARQ-863: -------------------------------- Summary: Poor error message when WebArchive deployed with ".jar" name Key: ARQ-863 URL: https://issues.jboss.org/browse/ARQ-863 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR8 Environment: Jboss AS 7.1.1.Final java version "1.7.0_01" Java(TM) SE Runtime Environment (build 1.7.0_01-b08) Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode) Linux ayaki.localdomain 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Reporter: Craig Ringer Priority: Minor If a WebArchive is deployed with the name ending in ".jar" instead of ".war" (due to, eg, a stupid editing mistake) the error message is not at all helpful. The container will fail to run the test class with a ClassNotFoundException for the test class. It'd be really nice if the deployer or the packager would detect this issue and report it. 13:58:42,082 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-1-thread-29) Failed: com.example.shrinkwrapwarbug.DemoTest.testReturnOne: java.lang.ClassNotFoundException: com.example.shrinkwrapwarbug.DemoTest from [Module "deployment.demo.jar:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA] at org.jboss.as.arquillian.service.ArquillianConfig.loadClass(ArquillianConfig.java:130) [arquillian-service:] at org.jboss.as.arquillian.service.ArquillianService$ExtendedTestClassLoader.loadTestClass(ArquillianService.java:259) [arquillian-service:] at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:124) [arquillian-service:] at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) [arquillian-service:] at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:226) [arquillian-service:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_01] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_01] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_01] at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_01] at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) [rt.jar:1.7.0_01] at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) [rt.jar:1.7.0_01] at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) [rt.jar:1.7.0_01] at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) [rt.jar:1.7.0_01] at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:250) [rt.jar:1.7.0_01] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_01] at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791) [rt.jar:1.7.0_01] at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034) at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_01] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_01] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_01] -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] (ARQ-835) Enable discarding commits from arquillian after tests are finished

by Jan Papousek (JIRA)

Jan Papousek created ARQ-835: -------------------------------- Summary: Enable discarding commits from arquillian after tests are finished Key: ARQ-835 URL: https://issues.jboss.org/browse/ARQ-835 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OpenShift Containers Affects Versions: 1.0.0.Beta1 Reporter: Jan Papousek Assignee: Jan Papousek When Arquillian Container OpenShift Express is used very often, it slows down the deployment (the history of GIT repository is larger and larger). There should be possibility to discard commits from arquillian to keep the history of GIT repository clean. -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-567) Supporting Test Suites (@ArquillianSuite)

by Mousavi Jahan Abadi S. M. (JIRA)

Supporting Test Suites (@ArquillianSuite) ----------------------------------------- Key: ARQ-567 URL: https://issues.jboss.org/browse/ARQ-567 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mousavi Jahan Abadi S. M. Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: @RunWith(ArquillianSuite.class) @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) public class AllTests{ @Deployment public static JavaArchive createTestArchive(){ return ShrinkWrap.create(JavaArchive.class,"test.jar"); } } The advantages of above approach for users of Arquillian framework are: - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. The advantage of above approach for framework itself is: - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
5
0 / 0

[JBoss JIRA] Created: (ARQ-271) TestEnricher should be called in @BeforeClass as well

by Thomas Diesler (JIRA)

TestEnricher should be called in @BeforeClass as well ----------------------------------------------------- Key: ARQ-271 URL: https://jira.jboss.org/browse/ARQ-271 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler The TestEnricher API could be extended such that static fields can be initialized. @Inject public static BundleContext context; @BeforeClass public static void beforeClass() { System.out.println("BeforeClass: " + context); } There would be two calls to TestEnricher. #1 After test class load, but before a call to @BeforeClass. #2 After instantiation of the test class, but before a call to @Before (#2 is the current behaviour) -- 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, 2 months

4
10
0 / 0

[JBoss JIRA] (ARQ-875) Use AS7 Deploy Ping Servlet to extract ProtocolMetadata

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-875: --------------------------------- Summary: Use AS7 Deploy Ping Servlet to extract ProtocolMetadata Key: ARQ-875 URL: https://issues.jboss.org/browse/ARQ-875 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OpenShift Containers Affects Versions: openshift_1.0.0.Beta1 Reporter: Aslak Knutsen Assignee: Karel Piwko Instead of doing Archive scanning to figure out the ProtocolMetadata, we could reuse the Ping Servlet we use to check if the deployment is done to return the ProtocolMetadata from inside the server. The Wait For: https://github.com/arquillian/arquillian-container-openshift/blob/master/... The Extractor: https://github.com/arquillian/arquillian-container-openshift/blob/master/... Similar MGM API Calls from AS7: https://github.com/jbossas/jboss-as/blob/master/arquillian/common/src/mai... -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] (ARQGRA-139) Blog about releasing Graphene 1 Final

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-139: --------------------------------- Summary: Blog about releasing Graphene 1 Final Key: ARQGRA-139 URL: https://issues.jboss.org/browse/ARQGRA-139 Project: Arquillian Graphene Issue Type: Task Components: planning Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Final -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (ARQ-876) Enable --admin-only start for AS7

by Galder Zamarreño (JIRA)

Galder Zamarreño created ARQ-876: ------------------------------------ Summary: Enable --admin-only start for AS7 Key: ARQ-876 URL: https://issues.jboss.org/browse/ARQ-876 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBoss AS Containers Reporter: Galder Zamarreño Enable AS7 to be started with --admin-only. This is very useful is you wanna do this: - Start AS - Install an extension+subsystem. - Reload the server - Deploy and hit the site More globally, a bunch of command line options should be possible to set for AS7 startup sequence, including --admin-only. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.sy... ] SBS JIRA Integration updated ARQ-814: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/5 (was: https://github.com/arquillian/arquillian-container-weld/pull/5) Forum Reference: https://community.jboss.org/message/723176#723176 > Should support injection of EJBs (as CDI Beans) in Weld Embedded > ---------------------------------------------------------------- > > Key: ARQ-814 > URL: https://issues.jboss.org/browse/ARQ-814 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Anthony O. > Assignee: Marko Lukša > Attachments: EJBTest.java > > > As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said. > {code} > @RunWith(Arquillian.class) > public class EJBTest { > @Deployment > public static JavaArchive createTestArchive() { > return ShrinkWrap > .create(JavaArchive.class, "test.jar") > .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > } > @Stateless > public static class SomeService { > public String someMethod() { > return "test"; > } > } > @Inject > SomeService someService; > @Test > public void testStatelessCall() { > Assert.assertEquals("test", someService.someMethod()); > } > } > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-764) Using DBUnit with IDENTITY or auto-increment columns

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-764: ---------------------------------- Summary: Using DBUnit with IDENTITY or auto-increment columns Key: ARQ-764 URL: https://issues.jboss.org/browse/ARQ-764 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Environment: MS SQL Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next MSSQL doesn't allow INSERTs with values specified for autoincrement columns. Provide a way to set the DatabaseOperation to one of the InsertIdentityOperation choices. -- 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, 2 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2012