March 2011 - arquillian-issues - Jboss List Archives

[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-398) Help GlassFish understand relative URIs

by Aslak Knutsen (JIRA)

Help GlassFish understand relative URIs --------------------------------------- Key: ARQ-398 URL: https://issues.jboss.org/browse/ARQ-398 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.Alpha5 Reporter: Aslak Knutsen Priority: Minor Fix For: 1.0.0.Beta1 The GlassFish Embedded 3.1 Container supports configurationXML in configuration, but this option delegated directly to GlassFish only supports absolute URIs. e.g. file:///home/test/domain.xml Add some support for non absolute paths: test/domain.xml -> new File().toURI -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

9
13
0 / 0

[JBoss JIRA] Created: (ARQ-400) GlassFish Embedded 3.1 configuration is not validated

by Karel Piwko (JIRA)

GlassFish Embedded 3.1 configuration is not validated ----------------------------------------------------- Key: ARQ-400 URL: https://issues.jboss.org/browse/ARQ-400 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.Alpha5 Reporter: Karel Piwko GlassFishConfiguration is not validated, so if instanceRoot is missing it fails with an ugly exception: Could not setup GlassFish Embedded Runtime java.lang.RuntimeException: Could not setup GlassFish Embedded Runtime at org.jboss.arquillian.container.glassfish.embedded_3_1.GlassFishContainer.setup(GlassFishContainer.java:119) at org.jboss.arquillian.container.glassfish.embedded_3_1.GlassFishContainer.setup(GlassFishContainer.java:51) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController$4.perform(ContainerLifecycleController.java:126) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController$4.perform(ContainerLifecycleController.java:106) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:183) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController.setupContainer(ContainerLifecycleController.java:105) at org.jboss.arquillian.impl.core.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.impl.core.EventContextImpl.invokeObservers(EventContextImpl.java:98) at org.jboss.arquillian.impl.core.EventContextImpl.proceed(EventContextImpl.java:80) at org.jboss.arquillian.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:78) at org.jboss.arquillian.impl.core.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.impl.core.EventContextImpl.proceed(EventContextImpl.java:87) at org.jboss.arquillian.impl.core.ManagerImpl.fire(ManagerImpl.java:126) at org.jboss.arquillian.impl.core.ManagerImpl.fire(ManagerImpl.java:106) at org.jboss.arquillian.impl.core.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController$1.perform(ContainerLifecycleController.java:68) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController$1.perform(ContainerLifecycleController.java:61) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController.forEachContainer(ContainerLifecycleController.java:176) at org.jboss.arquillian.impl.client.container.ContainerLifecycleController.setupContainers(ContainerLifecycleController.java:60) at org.jboss.arquillian.impl.core.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.impl.core.EventContextImpl.invokeObservers(EventContextImpl.java:98) at org.jboss.arquillian.impl.core.EventContextImpl.proceed(EventContextImpl.java:80) at org.jboss.arquillian.impl.core.ManagerImpl.fire(ManagerImpl.java:126) at org.jboss.arquillian.impl.core.ManagerImpl.fire(ManagerImpl.java:106) at org.jboss.arquillian.impl.core.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.impl.client.ContainerEventController.execute(ContainerEventController.java:54) at org.jboss.arquillian.impl.core.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.impl.core.EventContextImpl.invokeObservers(EventContextImpl.java:98) at org.jboss.arquillian.impl.core.EventContextImpl.proceed(EventContextImpl.java:80) at org.jboss.arquillian.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) at org.jboss.arquillian.impl.core.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.impl.core.EventContextImpl.proceed(EventContextImpl.java:87) at org.jboss.arquillian.impl.core.ManagerImpl.fire(ManagerImpl.java:126) at org.jboss.arquillian.impl.core.ManagerImpl.fire(ManagerImpl.java:106) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:58) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:86) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) Caused by: org.glassfish.embeddable.GlassFishException: org.jvnet.hk2.component.ComponentException: Failed to create a habitat at com.sun.enterprise.glassfish.bootstrap.StaticGlassFishRuntime.newGlassFish(StaticGlassFishRuntime.java:129) at org.jboss.arquillian.container.glassfish.embedded_3_1.GlassFishContainer.setup(GlassFishContainer.java:115) Caused by: org.jvnet.hk2.component.ComponentException: Failed to create a habitat at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.createHabitat(AbstractModulesRegistryImpl.java:169) at com.sun.enterprise.module.bootstrap.Main.createHabitat(Main.java:425) at com.sun.enterprise.glassfish.bootstrap.StaticGlassFishRuntime.newGlassFish(StaticGlassFishRuntime.java:104) Caused by: java.lang.NullPointerException at com.sun.hk2.component.ExistingSingletonInhabitant.<init>(ExistingSingletonInhabitant.java:57) at org.glassfish.config.support.DomainXml.decorate(DomainXml.java:139) at org.glassfish.config.support.DomainXml.decorate(DomainXml.java:139) (DomainXml.java:133) at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.populateConfig(AbstractModulesRegistryImpl.java:176) at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.createHabitat(AbstractModulesRegistryImpl.java:158) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

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

[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

13 years, 2 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

13 years, 2 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

13 years, 2 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

13 years, 2 months

4
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2011