August 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-452) NPE in ServletUtil.determineBaseURI(ServletUtil.java:44) with multiple @Deployment methods that have non-unique names (or no name)

by Joshua Davis (JIRA)

NPE in ServletUtil.determineBaseURI(ServletUtil.java:44) with multiple @Deployment methods that have non-unique names (or no name) ---------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-452 URL: https://issues.jboss.org/browse/ARQ-452 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Alpha5 Environment: Maven 3, Linux, Arquillian 1.0.0.Alpha5 Reporter: Joshua Davis When there are multiple {{@Deployment}} methods in a test, and the {{@Deployment}}s have the same name Arquillian will throw a {{NullPointerException}}: {code} testSomething(eg.domainmodel.UserTest) Time elapsed: 0.019 sec <<< ERROR! java.lang.NullPointerException at org.jboss.arquillian.protocol.servlet.ServletUtil.determineBaseURI(ServletUtil.java:44) at org.jboss.arquillian.protocol.servlet.BaseServletProtocol.getExecutor(BaseServletProtocol.java:56) at org.jboss.arquillian.protocol.servlet.BaseServletProtocol.getExecutor(BaseServletProtocol.java:30) at org.jboss.arquillian.impl.execution.RemoteTestExecuter.getContainerMethodExecutor(RemoteTestExecuter.java:105) at org.jboss.arquillian.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (ARQ-555) readme.txt has wrong Source Code URL

by Steven Boscarine (JIRA)

readme.txt has wrong Source Code URL ------------------------------------ Key: ARQ-555 URL: https://issues.jboss.org/browse/ARQ-555 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Steven Boscarine Priority: Minor Arquillian has moved to GIT, but the readme.txt (https://github.com/arquillian/arquillian-core/blob/master/readme.txt) is pointing to subversion. Source Code: http://anonsvn.jboss.org/repos/common/arquillian/trunk -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-568) Allow setting default container in arquillian.xml containing group definitions

by Richard Achmatowicz (JIRA)

Allow setting default container in arquillian.xml containing group definitions ------------------------------------------------------------------------------ Key: ARQ-568 URL: https://issues.jboss.org/browse/ARQ-568 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Richard Achmatowicz The <container/> element has a default attribute. If default="true", then this container will be started if no arquillian.launcher container name is specified. If default="false", then this container will not be started unless arquillian.launcher points to it. The <group/> element is used to define a group of containers to be started. However, the group element has no "default" attribute (see http://www.jboss.org/schema/arquillian/arquillian-1.0.xsd). So, if we have a configuration involving a single container and as group of containers in the same arquillian.xml file, such as: <arquillian> <container qualifier="X"/> <group qualifier="Y"/> </arquillian> then we cannot make Y the default. We should be able to specify that a group configuration is the default to be started among a set of configurations, and so group should have a default attribute as well. NOTE: when used within a <group/> the "default" attribute of container changes its meaning. According to AK: "default="true" on a /container means this is the default Configuration used if no arquillian.launch is specified. While for a Group it's the default container to use if no @TargetsContainer is used." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-564) Upgrade to ShrinkWrap Descriptors 1.1.0-alpha-3

by Andrew Rubinger (JIRA)

Upgrade to ShrinkWrap Descriptors 1.1.0-alpha-3 ----------------------------------------------- Key: ARQ-564 URL: https://issues.jboss.org/browse/ARQ-564 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Rubinger Assignee: Andrew Rubinger Upgrade to bring in new SPI and refactor as necessary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (ARQ-410) NPE in ContainerDeployController.forEachManagedDeployment() on web.xml parse error.

by Ondrej Zizka (JIRA)

NPE in ContainerDeployController.forEachManagedDeployment() on web.xml parse error. ----------------------------------------------------------------------------------- Key: ARQ-410 URL: https://issues.jboss.org/browse/ARQ-410 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Environment: 1.0.0.alpha5 Reporter: Ondrej Zizka I had errorneous in-container-web.xml, so parsing it failed with ContainerDeployController.forEachManagedDeployment . Successively, Arquillian threw the exception below. To reproduce, you can run Tomcat remote container from the commit [tomcat e7572f3] Some progress with ArquillianServletRunner from https://github.com/OndraZizka/arquillian . org.jboss.arquillian.container.tomcat.remote_6.TomcatRemoteInContainerTestCase Time elapsed: 1.419 sec <<< ERROR! java.lang.NullPointerException at org.jboss.arquillian.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:204) at org.jboss.arquillian.impl.client.container.ContainerDeployController.undeployManaged(ContainerDeployController.java:99) 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.jboss.arquillian.impl.core.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.impl.core.EventContextImpl.invokeObservers(EventContextImpl.java:98) Full ST attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
14
0 / 0

[JBoss JIRA] Created: (ARQ-328) EJB-API dependencies in Weld EE container should be optional (causes failures on boot)

by Lincoln Baxter III (JIRA)

EJB-API dependencies in Weld EE container should be optional (causes failures on boot) -------------------------------------------------------------------------------------- Key: ARQ-328 URL: https://jira.jboss.org/browse/ARQ-328 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Alpha4 Reporter: Lincoln Baxter III EJB APIs should be optional. If users do not supply the API jars, then EJB services should not attempt to load. This would enable easier configuration for those users who do not need EJB services, who only want Weld in EE-like container. Currently the ejb-api maven dependency is required. java.lang.NoClassDefFoundError: javax/ejb/Stateless at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.findEjbs(Ejbs.java:38) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.createEjbDescriptors(Ejbs.java:25) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:81) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.<init>(TestContainer.java:215) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:76) at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(ContainerDeployer.java:62) at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(ContainerDeployer.java:50) 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.beforeClass(EventTestRunnerAdaptor.java:96) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:162) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:24) 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.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) Caused by: java.lang.ClassNotFoundException: javax.ejb.Stateless at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 28 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

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQAJO-41) Create functional test for HTTP Basic authorization

by Karel Piwko (JIRA)

Create functional test for HTTP Basic authorization --------------------------------------------------- Key: ARQAJO-41 URL: https://issues.jboss.org/browse/ARQAJO-41 Project: Arquillian Ajocado Issue Type: Task Affects Versions: 1.0.0.Alpha2 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Alpha3 Provide a function test to test functionality provided by HTTP Basic authorization. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-562) Parameter injection for TestNG does not work

by Karel Piwko (JIRA)

Parameter injection for TestNG does not work -------------------------------------------- Key: ARQ-562 URL: https://issues.jboss.org/browse/ARQ-562 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.CR4 Environment: AS 7.0.1 web profile Surefire 2.9 TestNG 5.14.6 Reporter: Karel Piwko While trying to inject @ArquillianResource as method parameter such as {code} public class LowercaseConverterTest extends Arquillian { @Inject private LowercaseConverter lowercaseConverter; @ArquillianResource URL context; @Deployment public static JavaArchive createTestArchive() { return ShrinkWrap .create(JavaArchive.class, "test.jar") .addClasses(LowercaseConverter.class) .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); } /** * */ @Test public void testConvertToLowercase(@ArquillianResource URL foobar) { Assert.assertEquals("martin", lowercaseConverter.convertToLowercase("Martin")); } } {code} I'm getting following exception: {code} org.testng.TestNGException: Method testConvertToLowercase requires 1 parameters but 0 were supplied in the @Test annotation. at org.testng.internal.Parameters.checkParameterTypes(Parameters.java:187) at org.testng.internal.Parameters.createParameters(Parameters.java:123) at org.testng.internal.Parameters.createParameters(Parameters.java:357) at org.testng.internal.Parameters.handleParameters(Parameters.java:433) at org.testng.internal.Invoker.handleParameters(Invoker.java:1315) at org.testng.internal.Invoker.createParameters(Invoker.java:1022) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1122) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at org.testng.TestRunner.runWorkers(TestRunner.java:1147) at org.testng.TestRunner.privateRun(TestRunner.java:749) at org.testng.TestRunner.run(TestRunner.java:600) at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274) at org.testng.SuiteRunner.run(SuiteRunner.java:223) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1039) at org.testng.TestNG.runSuitesLocally(TestNG.java:964) at org.testng.TestNG.run(TestNG.java:900) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:113) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:207) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-80) Complete Documentation

by Lukáš Fryč (JIRA)

Complete Documentation ---------------------- Key: ARQAJO-80 URL: https://issues.jboss.org/browse/ARQAJO-80 Project: Arquillian Ajocado Issue Type: Feature Request Components: doc Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Final Complete the documentation, stub from migrated richfaces-selenium docs is here: https://docs.jboss.org/author/display/ARQAJO/Home -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQAJO-83) Update Selenium version to 2.2.0

by Karel Piwko (JIRA)

Update Selenium version to 2.2.0 -------------------------------- Key: ARQAJO-83 URL: https://issues.jboss.org/browse/ARQAJO-83 Project: Arquillian Ajocado Issue Type: Component Upgrade Components: core Affects Versions: 1.0.0.CR1 Reporter: Karel Piwko Assignee: Lukáš Fryč Fix For: 1.0.0.Final Update to latest stable selenium version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2011