December 2010 - arquillian-issues

[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

[JBoss JIRA] Created: (ARQ-342) Application/Module name of the form "jsr88-851802189695127335 instead of archive name, eg "test"

by Jesse Hutton (JIRA)

Application/Module name of the form "jsr88-851802189695127335 instead of archive name, eg "test" ------------------------------------------------------------------------------------------------ Key: ARQ-342 URL: https://jira.jboss.org/browse/ARQ-342 Project: Arquillian Issue Type: Bug Reporter: Jesse Hutton -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-307) In an EAR deployment, allow the customization of test.war

by Marius Bogoevici (JIRA)

In an EAR deployment, allow the customization of test.war --------------------------------------------------------- Key: ARQ-307 URL: https://jira.jboss.org/browse/ARQ-307 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Marius Bogoevici In an EAR deployment, the test.war attached by arquillian replaces a test.war configuration provided by the user. Ideally, it should be possible to allow test writers to attach artifacts to 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-176) Create integration tests for all CDI related deployment scenarios

by Aslak Knutsen (JIRA)

Create integration tests for all CDI related deployment scenarios ----------------------------------------------------------------- Key: ARQ-176 URL: https://jira.jboss.org/browse/ARQ-176 Project: Arquillian Issue Type: Task Components: Integration Test Suite Reporter: Aslak Knutsen Create a deployment integration test suite for all possible CDI related deployment types. EJB, WAR, JAR 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-104) TestEnrichment TestCase injection null in @Before

by Aslak Knutsen (JIRA)

TestEnrichment TestCase injection null in @Before ------------------------------------------------- Key: ARQ-104 URL: https://jira.jboss.org/jira/browse/ARQ-104 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha1 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Alpha2 Injection is done in the @Test cycle, should be moved to @Before cycle so one can setup injected resources before test is executed. -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-106) AfterSuite event is never called with JUnit

by Aslak Knutsen (JIRA)

AfterSuite event is never called with JUnit ------------------------------------------- Key: ARQ-106 URL: https://jira.jboss.org/jira/browse/ARQ-106 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Affects Versions: 1.0.0.Alpha1 Reporter: Aslak Knutsen Currently using a JVM Shutdown hook to call AfterSuite. This is never called. -- 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, 12 months

2
12
0 / 0

[JBoss JIRA] Created: (ARQ-341) Cannot test bean that @Observes CDI events

by gilad bar orion (JIRA)

Cannot test bean that @Observes CDI events ------------------------------------------ Key: ARQ-341 URL: https://jira.jboss.org/browse/ARQ-341 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: 1.0.0.Alpha4 Environment: arquillian-weld-ee-embedded-1.1 weld-core-bom:1.1.0.Beta1/Beta2 Reporter: gilad bar orion Cannot test beans with CDI events when using weld 1.1.0.Beta1 getting: java.lang.NoSuchMethodError: javax.enterprise.event.Observes.receive()Ljavax/enterprise/event/Reception (this is due to a naming change - https://jira.jboss.org/browse/WELD-699) when using weld 1.1.0.Beta2 getting: java.lang.NoClassDefFoundError: org/jboss/weld/bootstrap/api/helpers/ForwardingLifecycle at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) 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) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.<init>(TestContainer.java:214) 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.testng.Arquillian.arquillianBeforeClass(Arquillian.java:77) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) at org.apache.maven.surefire.Surefire.run(Surefire.java:180) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) Caused by: java.lang.ClassNotFoundException: org.jboss.weld.bootstrap.api.helpers.ForwardingLifecycle 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) ... 49 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (ARQ-344) PO'ify the Reference Guide for translation and upload it to translate.jboss.org

by Aslak Knutsen (JIRA)

PO'ify the Reference Guide for translation and upload it to translate.jboss.org ------------------------------------------------------------------------------- Key: ARQ-344 URL: https://jira.jboss.org/browse/ARQ-344 Project: Arquillian Issue Type: Feature Request Components: Documentation Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen Assignee: Dan Allen We should expose the Arquillian documentation at translate.jboss.org. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2010