November 2010 - arquillian-issues

[JBoss JIRA] Created: (ARQ-284) Configuration options should be loadable from multiple sources

by Aslak Knutsen (JIRA)

Configuration options should be loadable from multiple sources -------------------------------------------------------------- Key: ARQ-284 URL: https://jira.jboss.org/browse/ARQ-284 Project: Arquillian Issue Type: Feature Request Components: Configuration Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 The configuration should be able to get configuration from multiple locations and override in some order.. system properties, properties file, maven config, arquillian.xml 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

5
6
0 / 0

[JBoss JIRA] Created: (ARQ-336) Inject container references in the test to start/stop containers

by Jean Deruelle (JIRA)

Inject container references in the test to start/stop containers ---------------------------------------------------------------- Key: ARQ-336 URL: https://jira.jboss.org/browse/ARQ-336 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Reporter: Jean Deruelle Useful to test HA configuration and failover. Start 3 instances of JBoss AS in cluster mode target one of them and be able to kill it and start new nodes on demand to test failover. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

12
35
0 / 0

[JBoss JIRA] Created: (ARQ-236) Should be able to configure the Container lifecycle based on the Test events

by Aslak Knutsen (JIRA)

Should be able to configure the Container lifecycle based on the Test events ---------------------------------------------------------------------------- Key: ARQ-236 URL: https://jira.jboss.org/browse/ARQ-236 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen A user should be able to customize how he wants the Container to be controlled. The default behavior is: @BeforeSuite -> container.start() @BeforeClass -> container.deploy() @AfterClass -> container.undeploy() @AfterSuite -> container.stop() Other scenarios are: - Restart server pr test class @BeforeClass -> container.start() @BeforeClass -> container.deploy() @AfterClass -> container.undeploy() @AfterClass -> container.stop() - Redeploy pr test method @BeforeSuite -> container.start() @Before -> container.deploy() @After -> container.undeploy() @AfterSuite -> container.stop() - Restart pr test method @Before -> container.start() @Before -> container.deploy() @After -> container.undeploy() @After -> container.stop() This could be done by adding a Engine configuration option e.g.: engine/containerLifeCycle PrSuite|PrClass|PrMethod this option would map to different ContextAppenders in the background that does the setup/ordering. -- 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, 1 month

9
11
0 / 0

[JBoss JIRA] Created: (ARQ-49) Arquillian depends upon ShrinkWrap internals

by Andrew Lee Rubinger (JIRA)

Arquillian depends upon ShrinkWrap internals -------------------------------------------- Key: ARQ-49 URL: https://jira.jboss.org/jira/browse/ARQ-49 Project: Arquillian Issue Type: Task Reporter: Andrew Lee Rubinger Caught that a few Arquillian classes are directly depending upon ShrinkWrap internals, for which we cannot provide guarantee of consistency between releases. [alr@localhost trunk]$ egrep 'shrinkwrap.impl' -R . |grep .java ./demo/src/test/java/com/acme/cdi/InjectionTestCase.java:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; ./demo/src/test/java/com/acme/cdi/.svn/text-base/InjectionTestCase.java.svn-base:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; ./impl-base/src/main/java/org/jboss/arquillian/impl/ArquillianDeploymentAppender.java: Package.getPackage("org.jboss.shrinkwrap.impl.base"), ./impl-base/src/main/java/org/jboss/arquillian/impl/.svn/text-base/ArquillianDeploymentAppender.java.svn-base: Package.getPackage("org.jboss.shrinkwrap.impl.base"), ./junit/src/main/java/org/jboss/arquillian/junit/JUnitTestRunner.java:import org.jboss.shrinkwrap.impl.base.Validate; ./junit/src/main/java/org/jboss/arquillian/junit/.svn/text-base/JUnitTestRunner.java.svn-base:import org.jboss.shrinkwrap.impl.base.Validate; ./testng/src/main/java/org/jboss/arquillian/testng/TestNGTestRunner.java:import org.jboss.shrinkwrap.impl.base.Validate; ./testng/src/main/java/org/jboss/arquillian/testng/.svn/text-base/TestNGTestRunner.java.svn-base:import org.jboss.shrinkwrap.impl.base.Validate; ./demo-testng/src/test/java/com/acme/cdi/InjectionTestCase.java:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; ./demo-testng/src/test/java/com/acme/cdi/.svn/text-base/InjectionTestCase.java.svn-base:import org.jboss.shrinkwrap.impl.base.asset.ByteArrayAsset; Likely we'll want to evaluate these dependencies and instead move to API-only (for compile time, runtime requiring ShrinkWrap impls in "test" scope). -- 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, 1 month

6
10
0 / 0

[JBoss JIRA] Created: (ARQ-108) Should publish Arquillian artifacts to maven central

by Aslak Knutsen (JIRA)

Should publish Arquillian artifacts to maven central ---------------------------------------------------- Key: ARQ-108 URL: https://jira.jboss.org/jira/browse/ARQ-108 Project: Arquillian Issue Type: Task Components: Build Infrastructure Reporter: Aslak Knutsen Using the new Nexus repos we can auto publish to Maven Central. Not all of the containers are in Central as of no, so we need to split up the build. core + enrichers + packagers + examples + protocols - weld-embedded, openejb, openwebbeans-embedded should be able to go to central. -- 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, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (ARQ-138) Implement a remote Weblogic Server container

by Dan Allen (JIRA)

Implement a remote Weblogic Server container -------------------------------------------- Key: ARQ-138 URL: https://jira.jboss.org/jira/browse/ARQ-138 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha1 Reporter: Dan Allen Priority: Optional Fix For: 1.0.0.Alpha5 We have interest from the community in contributing container support for a remote Weblogic Server. This issue will track the progress of the contribution. Note: The proper abbreviation for Weblogic Server is wls -- 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, 1 month

11
17
0 / 0

[JBoss JIRA] Created: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote

by Dan Allen (JIRA)

Consolidate the remote host configuration for GlassFish Remote -------------------------------------------------------------- Key: ARQ-269 URL: https://jira.jboss.org/browse/ARQ-269 Project: Arquillian Issue Type: Feature Request Components: GlassFish Containers Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.Alpha4 In order for the GlassFish Remote container to target a remote host (rather than localhost), two separate properties must be set: deploymentUri remoteServerAddress The deploymentUri should really be an internal setting, dynamically set based on the following two configuration values: remoteServerAddress remoteServerAdminPort This hides the more cryptic deploymentUri value and exposes more user-friendly configuration, less prone to errors. -- 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, 2 months

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-312) Add TabLibConfiguration to Jetty plus container

by Dan Allen (JIRA)

Add TabLibConfiguration to Jetty plus container ----------------------------------------------- Key: ARQ-312 URL: https://jira.jboss.org/browse/ARQ-312 Project: Arquillian Issue Type: Bug Components: Jetty Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Assignee: Dan Allen The TagLibConfiguration was left out of the context configurations in the Jetty containers. This was done to speed up loading. However, some frameworks, such as JSF, use TLD files to register listeners. So those are broken as a result. The TagLibConfiguration needs to be added, or the user needs to be allow to configure this support via the container configuration. -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-157) OpenEJB container needs CDI-API to run

by Aslak Knutsen (JIRA)

OpenEJB container needs CDI-API to run -------------------------------------- Key: ARQ-157 URL: https://jira.jboss.org/browse/ARQ-157 Project: Arquillian Issue Type: Bug Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Andrew Lee Rubinger The OpenEJBTestEnricher needs CDI to run due to import of javax.inject.Inject -- 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, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (ARQ-308) Patch to support OpenEJB 3.2 API change

by Dan Allen (JIRA)

Patch to support OpenEJB 3.2 API change --------------------------------------- Key: ARQ-308 URL: https://jira.jboss.org/browse/ARQ-308 Project: Arquillian Issue Type: Patch Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 The Arquillian Embedded OpenEJB 3.1 container adapter works with OpenEJB 3.2 with the exception of one field reference. The public field AppInfo#jarPath was renamed to AppInfo#path. Attached is a patch which will determine the correct field name through reflection so both APIs can be supported. Keep in mind that OpenEJB 3.2 is still unreleased, so this is an enabling change (enables people to use it), and may be unnecessary if we find out why the field name was change. Or, perhaps, this issue will lead to an upstream change that makes this patch unnecessary. Either way, it would be nice to be able to use OpenEJB 3.2 as it supports JPA 2. -- 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, 2 months

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2010