January 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-67) Need to be able to deploy resources to the container alongside the primary deployment

by Pete Muir (JIRA)

Need to be able to deploy resources to the container alongside the primary deployment ------------------------------------------------------------------------------------- Key: ARQ-67 URL: https://jira.jboss.org/jira/browse/ARQ-67 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir For examples, tests will need to be able to deploy -ds.xml, JMS configuration files etc. -- 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

13 years, 9 months

5
19
0 / 0

[JBoss JIRA] Created: (ARQ-227) Support Deployment exception assert

by Aslak Knutsen (JIRA)

Support Deployment exception assert ----------------------------------- Key: ARQ-227 URL: https://jira.jboss.org/browse/ARQ-227 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Reporter: Aslak Knutsen For container / deployer / framework dev it is useful to be able to Assert on Deployment related issues. e.g. http://arquillian.pastebin.com/hPCh8yQd -- 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

13 years, 9 months

1
9
0 / 0

[JBoss JIRA] Created: (ARQ-353) Remove DeploymentScanner disabling

by Aslak Knutsen (JIRA)

Remove DeploymentScanner disabling ---------------------------------- Key: ARQ-353 URL: https://issues.jboss.org/browse/ARQ-353 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 The HDScanner / ProfileService redeploy issue has been fixed in JBoss AS 6.0 Final. Remove the old stop/start of HDScanner in the JBoss 6.0 Remote Container. New ProfileServiceClient API could be used to minimize the dep chain: dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-profileservice-client</artifactId> <version>6.0.0-SNAPSHOT</version> <type>pom</type> <scope>test</scope> </dependency> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-298) Implement conversations based on the new Weld context management API

by Pete Muir (JIRA)

Implement conversations based on the new Weld context management API -------------------------------------------------------------------- Key: ARQ-298 URL: https://jira.jboss.org/browse/ARQ-298 Project: Arquillian Issue Type: Bug Components: Weld Containers Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.0.Beta1 -- 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

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-164) NPE in DeployableTestBuilder

by Jesper Pedersen (JIRA)

NPE in DeployableTestBuilder ---------------------------- Key: ARQ-164 URL: https://jira.jboss.org/browse/ARQ-164 Project: Arquillian Issue Type: Bug Components: Deployable Containers SPI Affects Versions: 1.0.0.Alpha2 Reporter: Jesper Pedersen I get: java.lang.NullPointerException at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:82) at org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:71) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:68) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) Any component that uses a SPI implementation should guard against null values - if there is a non-null requirement of course - and throw an IllegalArgumentException with a descriptive error message. -- 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

13 years, 9 months

5
13
0 / 0

[JBoss JIRA] Created: (ARQ-329) Support Richfaces-Selenium in Selenium extension

by Karel Piwko (JIRA)

Support Richfaces-Selenium in Selenium extension ------------------------------------------------ Key: ARQ-329 URL: https://jira.jboss.org/browse/ARQ-329 Project: Arquillian Issue Type: Feature Request Components: Extension - Selenium Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Beta1 Selenium extension should support Richfaces-Selenium extension. This will involve creating a hook to the Arquillian test lifecycle and modification of Richfaces-Selenium to delegate the required functionality to the Arquilian-Selenium plugin. -- 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

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-281) NPE when JBOSS_HOME isn't set

by Pete Muir (JIRA)

NPE when JBOSS_HOME isn't set ----------------------------- Key: ARQ-281 URL: https://jira.jboss.org/browse/ARQ-281 Project: Arquillian Issue Type: Bug Components: JBoss Containers Affects Versions: 1.0.0.Alpha3 Reporter: Pete Muir org.jboss.arquillian.impl.event.FiredEventException: java.lang.NullPointerException 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:89) 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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:32) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:41) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:31) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.NullPointerException at org.jboss.jbossas.servermanager.ServerManager.getJavaEndorsedDirs(ServerManager.java:260) at org.jboss.jbossas.servermanager.ServerController.getEndorsedDirsProperty(ServerController.java:212) at org.jboss.jbossas.servermanager.ServerController.getStartCommandLine(ServerController.java:191) at org.jboss.jbossas.servermanager.ServerController.startServer(ServerController.java:101) at org.jboss.jbossas.servermanager.ServerManager.startServer(ServerManager.java:163) at org.jboss.arquillian.container.jbossas.managed_6.JBossASLocalContainer.start(JBossASLocalContainer.java:84) 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) ... 21 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

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-309) Allow configuration to specify an OpenEJB configuration resources (openejb.xml)

by Dan Allen (JIRA)

Allow configuration to specify an OpenEJB configuration resources (openejb.xml) ------------------------------------------------------------------------------- Key: ARQ-309 URL: https://jira.jboss.org/browse/ARQ-309 Project: Arquillian Issue Type: Feature Request Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Priority: Minor Implement the feature described in the OpenEJB FAQ for supplying a custom configuration file. http://openejb.apache.org/faq.html Create an openejb.xml file in any directory* that gets added to your test classpath. Then in your test case do this: protected void setUp() throws Exception { Properties properties = new Properties(); properties.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.apache.openejb.client.LocalInitialContextFactory"); URL config = this.getClass().getClassLoader().getResource("openejb.xml"); properties.setProperty("openejb.configuration", config.toExternalForm()); initialContext = new InitialContext(properties); } * The name of this file could be an Arquillian container configuration property. -- 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

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-215) Configuration should support loading of Configuration data for extensions/frameworks

by Aslak Knutsen (JIRA)

Configuration should support loading of Configuration data for extensions/frameworks ------------------------------------------------------------------------------------ Key: ARQ-215 URL: https://jira.jboss.org/browse/ARQ-215 Project: Arquillian Issue Type: Feature Request Components: Configuration Reporter: Aslak Knutsen Extensions / frameworks might need access to Configuration options. The Configuration should support dynamic loading of Configuration data for extensions as for Containers. e.g. <?xml version="1.0" encoding="UTF-8"?> <arquillian xmlns="http://jboss.com/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:coverage="urn:arq:org.jboss.arquillian.framework.cobertura"> <coverage:extension> <coverage:sourceFolder>src/main/java</coverage:sourceFolder> </coverage:extension> </arquillian> -- 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

13 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-340) mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations

by Radai Rosenblatt (JIRA)

mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations --------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-340 URL: https://jira.jboss.org/browse/ARQ-340 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha4 Environment: JRE 1.6.0.21 windows xp jboss embedded 6 Reporter: Radai Rosenblatt suppose i have an interface called BeanInterface, which is a local interface implemented a class called BeanImplementation. then, in my test case, i have the following in ijected field: @EJB(mappedName = "java:global/test/BeanImplementation/local") private BeanInterface bean; this will fail because the enricher does not bother looking at the annotation attributes. specifically, as can be seen in EJBInjectionEnricher.java line 102, the code does not pass the Field itself to the lookup method, only its name. the lookup method then proceeds to try several JNDI naming alternatives (line 137). this means that production classes are forced to adhere to the naming conventions used by arquillian code or tests fail. the code in question could take into account the mappedName and/or lookup attributes of @EJB to allow developers to specify the JNDI name for the lookup. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2011