July 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-433) Add a Tomcat 7 embedded container

by Ian Brandt (JIRA)

Add a Tomcat 7 embedded container --------------------------------- Key: ARQ-433 URL: https://issues.jboss.org/browse/ARQ-433 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: 1.0.0.Alpha5 Reporter: Ian Brandt Tomcat 7 has deprecated the {{[org.apache.catalina.startup.Embedded|http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Embedded.html]}} API as used by the {{arquillian-tomcat-embedded-6}} container implementation. The new API is {{[org.apache.catalina.startup.Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Tomcat.html]}}. That said I have no idea if the [new {{Tomcat}} API is mature or suitable|http://www.coderanch.com/t/513623/Tomcat/Tomcat-embedded-web-app...] for Arquillian at this time. Either way with Tomcat 7 implementing [Servlet 3.0's web fragments|http://java.sun.com/developer/technicalArticles/JavaEE/JavaEE6O...], which coincide nicely with Arquillian/ShrinkWrap by allowing one to package isolated parts of their production webapp configuration for select integration tests, I think it would be great if Arquillian declared Tomcat 7 as a supported container. This could be done by implementing the new API in an {{arquillian-tomcat-embedded-7}} container, forking the deprecated API from {{arquillian-tomcat-embedded-6}} to create the same, or just adding documentation that states the {{arquillian-tomcat-embedded-6}} container can and should be used for Tomcat 7 at this time. Thoughts? I'm going to plow ahead with {{arquillian-tomcat-embedded-6}} for now. If I run into a reason to fork it or create a container around the new API I'll try my hand at a pull request. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (ARQ-438) @DeploymentName and @OperatesOnDeployment could be made typesafe

by Karel Piwko (JIRA)

@DeploymentName and @OperatesOnDeployment could be made typesafe ---------------------------------------------------------------- Key: ARQ-438 URL: https://issues.jboss.org/browse/ARQ-438 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployable Containers SPI Affects Versions: 1.0.0.Alpha5 Reporter: Karel Piwko Priority: Minor Currently, multideployments are controlled by string based name, e.g. {code} @Deployment(name = "dep.active-1") @TargetsContainer("container.active-1") public static WebArchive createTestDeployment() { return Deployments.createActiveClient(); } @Test @OperateOnDeployment("dep.active-1") public void callActive1() throws Exception { int count = incrementCache(cache); System.out.println("Cache incremented, current count: " + count); Assert.assertEquals(1, count); } {code} Deployment.name can be switched to a meta annotation and than this functionality can be provided in a type-safe way, e.g. {code} @DeploymentTarget public @interface MyExtraDeployment {} public Test { @Deployment @MyExtraDeployment @TargetsContainer("container.active-1") public static WebArchive createTestDeployment() { return Deployments.createActiveClient(); } @Test @MyExtraDeployment public void callActive1() throws Exception { int count = incrementCache(cache); System.out.println("Cache incremented, current count: " + count); Assert.assertEquals(1, count); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-148) Support EL-like expressions for sysprops and env variables in arquillian.xml

by Andrew Lee Rubinger (JIRA)

Support EL-like expressions for sysprops and env variables in arquillian.xml ---------------------------------------------------------------------------- Key: ARQ-148 URL: https://jira.jboss.org/browse/ARQ-148 Project: Arquillian Issue Type: Feature Request Reporter: Andrew Lee Rubinger Likely we might need to rely on configuration available from the system or environment, so support usage like: <tag>${jboss.home}</tag> <tag>${env.jboss.home}</tag> ...inside arquillian.xml -- 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, 9 months

6
24
0 / 0

[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

12 years, 9 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

12 years, 9 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

12 years, 9 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

12 years, 9 months

3
5
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

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQAJO-46) Team Code Review

by Lukas Fryc (JIRA)

Team Code Review ---------------- Key: ARQAJO-46 URL: https://issues.jboss.org/browse/ARQAJO-46 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 1.0.0.Alpha3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQAJO-50) Review Ftest module Code, Style and JavaDoc

by Lukas Fryc (JIRA)

Review Ftest module Code, Style and JavaDoc ------------------------------------------- Key: ARQAJO-50 URL: https://issues.jboss.org/browse/ARQAJO-50 Project: Arquillian Ajocado Issue Type: Sub-task Reporter: Lukas Fryc Assignee: Juraj Huska Fix For: 1.0.0.Alpha3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2011