July 2010 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-228) Using Managed Container fails for first test case but runs the next

by Aslak Knutsen (JIRA)

Using Managed Container fails for first test case but runs the next ------------------------------------------------------------------- Key: ARQ-228 URL: https://jira.jboss.org/browse/ARQ-228 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Affects Versions: 1.0.0.Alpha3 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Alpha3 Managed Containers should not support to attach them selves to running instances to due to security issues. When running multiple test cases using the JBoss AS Managed 6 container, the first test case fail with "The server is already running!...", but the second test case deploys fine and runs. -- 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

15 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-165) Test class bundled with the deployment in a AS_CLIENT test

by Jozef Hartinger (JIRA)

Test class bundled with the deployment in a AS_CLIENT test ---------------------------------------------------------- Key: ARQ-165 URL: https://jira.jboss.org/browse/ARQ-165 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha2 Reporter: Jozef Hartinger Fix For: 1.0.0.Alpha3 Even though I use @Run(RunModeType.AS_CLIENT), the test class gets implicitly bundled with the application. This leads to deployment failures when using CDI-enabled container (client libraries like httpclient, arquillian, etc. are not available to the server). This issue can be solved by not implicitly bundling the test class when the test is run AS_CLIENT (The test class is not needed on the server anyway) -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-201) Primitive fields annotated with @Resource are not assigned

by Dan Allen (JIRA)

Primitive fields annotated with @Resource are not assigned ---------------------------------------------------------- Key: ARQ-201 URL: https://jira.jboss.org/browse/ARQ-201 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen Fields which are not null are skipped when performing @Resource injections. However, primitive fields are never null and therefore injections do not occur on those fields. Example: @Resource(name = "port") int port; -- 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

15 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-180) Create a DeployableContainer integration for Weld Embedded with Mock EE

by Aslak Knutsen (JIRA)

Create a DeployableContainer integration for Weld Embedded with Mock EE ----------------------------------------------------------------------- Key: ARQ-180 URL: https://jira.jboss.org/browse/ARQ-180 Project: Arquillian Issue Type: Feature Request Components: Weld Containers Reporter: Aslak Knutsen Assignee: Aslak Knutsen -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-186) Expose Java VM memory parameters as part of the Configuration for Managed containers

by Aslak Knutsen (JIRA)

Expose Java VM memory parameters as part of the Configuration for Managed containers ------------------------------------------------------------------------------------ Key: ARQ-186 URL: https://jira.jboss.org/browse/ARQ-186 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Reporter: Aslak Knutsen Expose memory settings as part of the Configuration object. MaxPermSize mx ms -- 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

15 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-97) Load classes and resources from ShrinkWrap archive

by Dan Allen (JIRA)

Load classes and resources from ShrinkWrap archive -------------------------------------------------- Key: ARQ-97 URL: https://jira.jboss.org/jira/browse/ARQ-97 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: 1.0.0.Alpha1 Reporter: Dan Allen Fix For: 1.0.0.Alpha2 When the test, or libraries used by the test, attempt to load a class or resource from the classpath, that request should be diverted to look in the ShrinkWrap archive defined by the test. Currently, this classloading operation is looking in the classpath visible to the test runner. This causes two problems: 1. resources in the ShrinkWrap archive are not found 2. the classpath available to the test case is leaking (only resources in the ShrinkWrap archive should be visible) The classpath needs to be constrained/protected. -- 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

15 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-179) Package rename deleted JBoss AS Local 5.1 Container

by Aslak Knutsen (JIRA)

Package rename deleted JBoss AS Local 5.1 Container --------------------------------------------------- Key: ARQ-179 URL: https://jira.jboss.org/browse/ARQ-179 Project: Arquillian Issue Type: Bug Components: JBoss Containers Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-202) Rename Local containers to Managed

by Aslak Knutsen (JIRA)

Rename Local containers to Managed ---------------------------------- Key: ARQ-202 URL: https://jira.jboss.org/browse/ARQ-202 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Priority: Minor 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-162) Add version to maven plugins (fixes maven 3 warnings)

by Sten Aksel Heien (JIRA)

Add version to maven plugins (fixes maven 3 warnings) ----------------------------------------------------- Key: ARQ-162 URL: https://jira.jboss.org/browse/ARQ-162 Project: Arquillian Issue Type: Patch Components: Build Infrastructure Affects Versions: 1.0.0.Alpha2 Reporter: Sten Aksel Heien The patch to build/pom.xml will get rid of maven 3 warning: 'reporting.plugins.plugin.version' is missing for org.codehaus.mojo: cobertura-maven-plugin + findbugs-maven-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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-181) When using @Text expected exception, the internal state of the TestResult is unknown

by Aslak Knutsen (JIRA)

When using @Text expected exception, the internal state of the TestResult is unknown ------------------------------------------------------------------------------------ Key: ARQ-181 URL: https://jira.jboss.org/browse/ARQ-181 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Reporter: Aslak Knutsen When using the ExpectedException feature in the TestFrameworks the internal TestResult object in Arquillian is in an unknown state. Arquillian catches the thrown exception, but the actual validation of it is done in the test framework after Arquillian is done with the test invocation. Arquillian can only know that a Exception has been thrown, but not if it is expected or not. JUnit @Test(expected=Exception.class) TestNG @Test(expectedException=Exception.class) @ExpectedException(Exception.class) Follow up with TestNG and JUnit to see how this can be done.. -- 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

15 years, 8 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2010