November 2010 - arquillian-issues

[JBoss JIRA] Created: (ARQ-279) Weld SE should support nested Jars

by Aslak Knutsen (JIRA)

Weld SE should support nested Jars ---------------------------------- Key: ARQ-279 URL: https://jira.jboss.org/browse/ARQ-279 Project: Arquillian Issue Type: Feature Request Components: Weld Containers Reporter: Aslak Knutsen In any larger app, Libraries are needed. Weld SE container should support the notion of Nested JavaArchives in the @Deployment. Should work about the same as for Weld EE, scan through the Archives recursively looking for class/beans.xml/extensions etc. -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (ARQ-286) Should support JUnit @Rules

by Aslak Knutsen (JIRA)

Should support JUnit @Rules --------------------------- Key: ARQ-286 URL: https://jira.jboss.org/browse/ARQ-286 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 Using the JUnit feature @Rule becomes a problem when running against Remote servers since the @Rule is executed both on the Client and Container side. It works fine in Embedded Containers since the Test is executed in the same VM, but if the Rule is dependent on Container features, the @Test will fail. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (ARQ-53) Research possibility of redirecting log statements back to client

by Aslak Knutsen (JIRA)

Research possibility of redirecting log statements back to client ----------------------------------------------------------------- Key: ARQ-53 URL: https://jira.jboss.org/jira/browse/ARQ-53 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen When running in remote containers all system.out/err and log statements done in the testcase are written to the server log. It should be possible to catch this and redirect them back to the client.. -- 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, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-264) Create a DeployableContainer integration for remote WebSphere

by Aslak Knutsen (JIRA)

Create a DeployableContainer integration for remote WebSphere ------------------------------------------------------------- Key: ARQ-264 URL: https://jira.jboss.org/browse/ARQ-264 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Priority: Minor -- 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, 7 months

4
16
0 / 0

[JBoss JIRA] Created: (ARQ-261) Add a Tomcat managed container

by Pete Muir (JIRA)

Add a Tomcat managed container ------------------------------ Key: ARQ-261 URL: https://jira.jboss.org/browse/ARQ-261 Project: Arquillian Issue Type: Feature Request Components: Tomcat Containers Affects Versions: 1.0.0.Alpha3 Reporter: Pete Muir -- 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, 7 months

5
7
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, 7 months

6
24
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, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-229) Should split API and Impl in two different modules

by Aslak Knutsen (JIRA)

Should split API and Impl in two different modules -------------------------------------------------- Key: ARQ-229 URL: https://jira.jboss.org/browse/ARQ-229 Project: Arquillian Issue Type: Feature Request Components: Extension - Performance Reporter: Aslak Knutsen Assignee: St?le Pedersen Fix For: 1.0.0.Alpha4 ContextAppenders are auto included in the runtime if found on ClassPath. We should consider splitting the performance extension into two modules, api and impl. Where API contains all the user facing annotations etc. With this you can compile against API and only include impl when you actually want to run the test case in performance 'mode', e.g. via a special profile. mvn test -P jbossas-remote-6,performance-test -- 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

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-315) add configuration property to JBoss AS containers to explode deployment

by Dan Allen (JIRA)

add configuration property to JBoss AS containers to explode deployment ----------------------------------------------------------------------- Key: ARQ-315 URL: https://jira.jboss.org/browse/ARQ-315 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 In some cases, it's necessary to have JBoss AS explode the deployment on the server. For instance, if the framework (such as Weld Servlet) uses archive scanning, it wouldn't be able to handle the VFS files. While a more formal solution may be appropriate, a stopgap measure is often to have the archive exploded once it arrives at the server. The DeploymentManager offers this option, and thus we should have a configuration property for it. -- 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
12
0 / 0

[JBoss JIRA] Created: (ARQ-163) Support for code coverage via Emma

by Pete Muir (JIRA)

Support for code coverage via Emma ---------------------------------- Key: ARQ-163 URL: https://jira.jboss.org/browse/ARQ-163 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir Priority: Critical Fix For: 1.0.0.Alpha3 -- 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

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2010