September 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQ-543) CDI injection into testcase does not work on GlassFish

by Jozef Hartinger (JIRA)

CDI injection into testcase does not work on GlassFish ------------------------------------------------------ Key: ARQ-543 URL: https://issues.jboss.org/browse/ARQ-543 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR1 Reporter: Jozef Hartinger Priority: Blocker Having the following testcase: @RunWith(Arquillian.class) public class FooTest { @Inject private Foo foo; @Deployment public static JavaArchive deploy() { return ShrinkWrap.create(JavaArchive.class, "foo.jar").addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml") .addClasses(Foo.class, FooTest.class); } @Test public void test() { Assert.assertNotNull(foo); } } public class Foo { } the test always fails on Glassfish while it works fine on JBoss AS 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-606) Glassfish JUnit test fails upon successful deploy (but with warnings)

by Pedro Kowalski (JIRA)

Glassfish JUnit test fails upon successful deploy (but with warnings) --------------------------------------------------------------------- Key: ARQ-606 URL: https://issues.jboss.org/browse/ARQ-606 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.CR1 Environment: GNU/Linux Ubuntu 11.04 x86 Reporter: Pedro Kowalski Arquillian controlled JUnit test is failing because of Glassfish WARNING: [#|2011-09-19T23:52:35.182+0200|WARNING|glassfish3.1.1|javax.org.glassfish.persistence.org.glassfish.persistence.common|_ThreadID=18;_ThreadName=admin-thread-pool-4848(2);|PER01000: Got SQLException executing statement "CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))": java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'.|#] The REST deployer returns: org.jboss.arquillian.container.spi.client.container.DeploymentException: "http://localhost:4848/management/domain/applications/application/test" created successfully. but the tests are failing. According to Glassfish team (http://java.net/projects/glassfish/lists/persistence/archive/2006-11/mess...) this message can be safely ignored. Suggestion: Apparently the deployer re-catches the exception and marks test as failed. The deployer should be aware of the return status (in this case the archive is deployed successfully) or check the thrown exception and react appropriately (i.e. ignore the above exception). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

7
10
0 / 0

[JBoss JIRA] Created: (ARQ-449) Add support for SSL on Admin console

by Aslak Knutsen (JIRA)

Add support for SSL on Admin console ------------------------------------ Key: ARQ-449 URL: https://issues.jboss.org/browse/ARQ-449 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: GlassFish Containers Environment: GlassFish Remote 3.1 Reporter: Aslak Knutsen ref: https://github.com/arquillian/arquillian-container-glassfish/commit/6da4a... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
4
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

14 years, 5 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

14 years, 5 months

9
13
0 / 0

[JBoss JIRA] Created: (ARQ-527) EAR deployment on remote container in server mode

by Rudolf Biczok (JIRA)

EAR deployment on remote container in server mode ------------------------------------------------- Key: ARQ-527 URL: https://issues.jboss.org/browse/ARQ-527 Project: Arquillian Issue Type: Patch Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.Alpha5 Environment: CentOS 5.5, Glassfish 3.1 Reporter: Rudolf Biczok Priority: Critical EAR deployment seems not to work in an in-container test-case, because the "list_sub_components" command in Glassfish behaves differently in case of EAR archives (it shows only the modules instead of the servlets). Adding different parameters to the "list_sub_components" command solves the issue for me -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
4
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

14 years, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (ARQ-450) Support dynamic generation of ProtocolMetadata

by Aslak Knutsen (JIRA)

Support dynamic generation of ProtocolMetadata ---------------------------------------------- Key: ARQ-450 URL: https://issues.jboss.org/browse/ARQ-450 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: GlassFish Containers Environment: GlassFish Remote 3.1 Reporter: Aslak Knutsen ref: https://github.com/arquillian/arquillian-container-glassfish/commit/6da4a... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-424) Create a DeployableContainer integration for embeddable WAS V8.0

by Gerhard Poul (JIRA)

Create a DeployableContainer integration for embeddable WAS V8.0 ---------------------------------------------------------------- Key: ARQ-424 URL: https://issues.jboss.org/browse/ARQ-424 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebSphere Containers Reporter: Gerhard Poul Priority: Optional Create a DeployableContainer integration for remote WebSphere Application Server V8.0 which will eGA June 17, 2011, and GA July 22, 2011. - Announcement letter: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-423) Create a DeployableContainer integration for remote WAS V8.0

by Gerhard Poul (JIRA)

Create a DeployableContainer integration for remote WAS V8.0 ------------------------------------------------------------ Key: ARQ-423 URL: https://issues.jboss.org/browse/ARQ-423 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebSphere Containers Reporter: Gerhard Poul Priority: Optional Create a DeployableContainer integration for remote WebSphere Application Server V8.0 which will eGA June 17, 2011, and GA July 22, 2011. - Announcement letter: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2011