February 2012 - arquillian-issues

[JBoss JIRA] (ARQ-742) Print the name of the container in the "Could not deploy to container" exception.

by Ondrej Zizka (JIRA)

Ondrej Zizka created ARQ-742: -------------------------------- Summary: Print the name of the container in the "Could not deploy to container" exception. Key: ARQ-742 URL: https://issues.jboss.org/browse/ARQ-742 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Base Implementation Reporter: Ondrej Zizka In multi-container tests, this exception lacks information about what server it failed to deploy to: {code} org.jboss.arquillian.container.spi.client.container.DeploymentException: Could not deploy to container: {"JBAS014671: Failed services" => {"jboss.ejb3.dd-based-ejb-client-context.\"client.jar\"" => "org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context.\"client.jar\": Failed to start service"}} at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:74) at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:142) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:156) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:123) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:266) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:122) ... {code} The exception is thrown in the ArchiveDeployer, but the implementation of DeployableContainer doesn't get this information so Arq must be changed itself. I suggest to throw an exception somewhere in ContainerDeployController with a message of this form: {code:java} throw new DeploymentException("Depoying of <deployment-name> to <container-name> failed: \n " + e.getMessage(), e); {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-602) Maven plugin - exception on shutdown

by Jozef Hartinger (JIRA)

Maven plugin - exception on shutdown ------------------------------------ Key: ARQ-602 URL: https://issues.jboss.org/browse/ARQ-602 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Maven Plugin Affects Versions: maven_1.0.0.Alpha1 Environment: JBoss AS 7.0.1.Final Reporter: Jozef Hartinger Fix For: maven_1.0.0.next I am getting the following exception after running arquillian:run with the jbossas-managed-7 container and using Ctrl+c to stop the server once it's started. Note that the application remains deployed and a subsequent attemp to run mvn arquillian:run causes duplicate deployment failure. ^Cjava.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:55) at java.lang.Runtime.removeShutdownHook(Runtime.java:220) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.stopInternal(ManagedDeployableContainer.java:155) at org.jboss.as.arquillian.container.CommonDeployableContainer.stop(CommonDeployableContainer.java:76) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$6.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$6.perform(ContainerLifecycleController.java:153) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:186) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.stopContainer(ContainerLifecycleController.java:152) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.maven.Utils.stop(Utils.java:64) at org.jboss.arquillian.maven.Run$1.run(Run.java:66) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] (ARQ-741) Copy cause exception message to DeploymentException: "Could not deploy to container".

by Ondrej Zizka (JIRA)

Ondrej Zizka created ARQ-741: -------------------------------- Summary: Copy cause exception message to DeploymentException: "Could not deploy to container". Key: ARQ-741 URL: https://issues.jboss.org/browse/ARQ-741 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (ARQ-722) Set ${arq.currentTest} and ${arq.server} for AS7 instances (using management).

by Ondrej Zizka (Created) (JIRA)

Set ${arq.currentTest} and ${arq.server} for AS7 instances (using management). ------------------------------------------------------------------------------ Key: ARQ-722 URL: https://issues.jboss.org/browse/ARQ-722 Project: Arquillian Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBoss Containers Affects Versions: 1.0.0.CR7 Reporter: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
2
0 / 0

[JBoss JIRA] (ARQ-740) jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created ARQ-740: ------------------------------------ Summary: jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs. Key: ARQ-740 URL: https://issues.jboss.org/browse/ARQ-740 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Trivial The xnio-api is probably the most dangerous one of these 3. It ships with xnio-api 3.0.0.Beta2, but some code requires 3.0.0.Beta3. {code} IncompatibleDependencyOverwrite error for org.jboss.logging:jboss-logging:3.0.0.GA paths to dependency are: +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.sasl:jboss-sasl:1.0.0.Beta2 +-org.jboss.logging:jboss-logging:3.0.0.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-testenricher-msc:7.0.2.Final +-org.jboss.logging:jboss-logging:3.0.1.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.osgi.spi:jbosgi-spi:1.0.28 +-org.jboss.logging:jboss-logging:3.0.0.Beta3 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-controller-client:7.0.2.Final +-org.jboss.as:jboss-as-protocol:7.0.2.Final +-org.jboss.logging:jboss-logging:3.0.1.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.osgi.spi:jbosgi-spi:1.0.28 +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 +-org.jboss.logging:jboss-logging:3.0.0.Beta3 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-controller-client:7.0.2.Final +-org.jboss.as:jboss-as-protocol:7.0.2.Final +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2 +-org.jboss.logging:jboss-logging:3.0.0.Beta5 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-jmx:7.0.2.Final +-org.jboss.as:jboss-as-server:7.0.2.Final +-org.jboss.as:jboss-as-controller:7.0.2.Final +-org.jboss.logging:jboss-logging:3.0.1.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-jmx:7.0.2.Final +-org.jboss.as:jboss-as-server:7.0.2.Final +-org.jboss.as:jboss-as-domain-http-api:7.0.2.Final +-org.jboss.logging:jboss-logging:3.0.1.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-jmx:7.0.2.Final +-org.jboss.as:jboss-as-server:7.0.2.Final +-org.jboss.as:jboss-as-deployment-repository:7.0.2.Final +-org.jboss.logging:jboss-logging:3.0.1.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-jmx:7.0.2.Final +-org.jboss.as:jboss-as-server:7.0.2.Final +-org.jboss.as:jboss-as-process-controller:7.0.2.Final +-org.jboss.logging:jboss-logging:3.0.1.GA and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final +-org.jboss.osgi.resolver:jbosgi-resolver-api:1.0.9 +-org.jboss.osgi.resolver:jbosgi-resolver-metadata:1.0.9 +-org.jboss.logging:jboss-logging:3.0.0.Beta3 , IncompatibleDependencyOverwrite error for org.jboss.xnio:xnio-api:3.0.0.Beta2 paths to dependency are: +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-controller-client:7.0.2.Final +-org.jboss.as:jboss-as-protocol:7.0.2.Final +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2 +-org.jboss.xnio:xnio-api:3.0.0.Beta2 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-controller-client:7.0.2.Final +-org.jboss.as:jboss-as-protocol:7.0.2.Final +-org.jboss.xnio:xnio-nio:3.0.0.Beta3 +-org.jboss.xnio:xnio-api:3.0.0.Beta3 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.as:jboss-as-jmx:7.0.2.Final +-org.jboss.as:jboss-as-server:7.0.2.Final +-org.jboss.as:jboss-as-remoting:7.0.2.Final +-org.jboss.xnio:xnio-api:3.0.0.Beta3 , IncompatibleDependencyOverwrite error for org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 paths to dependency are: +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final +-org.jboss.osgi.spi:jbosgi-spi:1.0.28 +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6 and +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final +-org.jboss.osgi.framework:jbosgi-framework-core:1.0.0.CR8 +-org.jboss.osgi.vfs:jbosgi-vfs30:1.0.6 +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6 {code} Maybe JBoss modules makes this not as bad as it is with normal maven projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
1
0 / 0

[JBoss JIRA] (ARQ-638) Option to "clean" the container before running tests

by Ondrej Zizka (Created) (JIRA)

Option to "clean" the container before running tests ---------------------------------------------------- Key: ARQ-638 URL: https://issues.jboss.org/browse/ARQ-638 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, JBoss Containers Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka It would be nice to have an option to have the container cleaned before launching it. For AS7 as an example, that would mean deleting * standalone/log * standalone/data * standalone/tmp * standalone/deployments (?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
4
0 / 0

[JBoss JIRA] (ARQ-710) Separated per-test and per-container log files.

by Ondrej Zizka (Created) (JIRA)

Separated per-test and per-container log files. ----------------------------------------------- Key: ARQ-710 URL: https://issues.jboss.org/browse/ARQ-710 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR7 Reporter: Ondrej Zizka Priority: Critical What's the best way to separate server and client log messages? Currently, any output is redirected to Surefire. Which only creates one output. So, either arq can log to an arbitrary file, or surefire could have support for multiple logs. The later won't happen any soon I guess Arq just forwards anything to surefire. So, let's say I want to have separated log files in surefire-reports dir: * org.jboss.FooBarTestCase-client, * org.jboss.FooBarTestCase-server1, * org.jboss.FooBarTestCase-server2, ... This feature is quite important for large testsuites which produce tons of log messages, and even more for multi-node tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
8
0 / 0

[JBoss JIRA] (ARQ-645) @ArquillianResource @OperatesOnDeployment("foo") URL; for multiple containers

by Marek Schmidt (Created) (JIRA)

@ArquillianResource @OperatesOnDeployment("foo") URL; for multiple containers ----------------------------------------------------------------------------- Key: ARQ-645 URL: https://issues.jboss.org/browse/ARQ-645 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Marek Schmidt It would be nice to support something like @Test @RunAsClient public void test(@ArquillianResource @OperatesOnDeployment("foo") URL foo, @ArquillianResource @OperatesOnDeployment("bar") URL foo) { ... } for functional clustering tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
4
0 / 0

[JBoss JIRA] (ARQ-670) Arquillian Servlet's context root should be "test", not "test.war", in EAR

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-670?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen resolved ARQ-670. ------------------------------- Resolution: Done pushed upstream > Arquillian Servlet's context root should be "test", not "test.war", in EAR > -------------------------------------------------------------------------- > > Key: ARQ-670 > URL: https://issues.jboss.org/browse/ARQ-670 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.0.0.CR6 > Reporter: Alexandre Gattiker > Assignee: Aslak Knutsen > Fix For: 1.0.0.Final > > > As the Arquillian JMX protocol doesn't currently work for EARs in AS7 (AS7-1696), I tried using the Servlet 3.0 protocol. However the test runner fails to contact the servlet: > java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/test/ArquillianServletRunner?outputMode=serializedO.... No result returned > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:158) > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:118) > ... 75 more > The servlet is actually deployed at: > http://127.0.0.1:8080/test.war/ArquillianServletRunner > Because Arquillian has added the following to my EAR's application.xml: > <module> > <web> > <web-uri>test.war</web-uri> > <context-root>test.war</context-root> > </web> > </module> > This can be traced to org.jboss.arquillian.protocol.servlet.v_3.ServletProtocolDeploymentPackager: > > applicationXml.webModule(wrappedWar.getName(), wrappedWar.getName()); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-739) Login simulation in tests with @LoginAs("username", "password") and an authenticated servlet protocol

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created ARQ-739: ------------------------------------ Summary: Login simulation in tests with @LoginAs("username", "password") and an authenticated servlet protocol Key: ARQ-739 URL: https://issues.jboss.org/browse/ARQ-739 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Motivation: 1) Testing the similar functionality under different logins (and therefore roles) should be easy. 2) Each in-container test is scope request. If you inject a request or session scoped bean in the test, that requires an Identity to be injected, it will be created with a dummy Identity (username = null). This can leave the bean in an illegal state (especially when using @PostConstruct or @Produces). Proposal A: {code} @Deployment @OverProtocol("Authenticated Servlet") public static WebArchive createDeployment() {...} @Test @LoginAs("admin", "admin") public void changeThemeAsAdmin() {...} @Test(exception = AuthenticationException.class) @LoginAs("guest", "guest") public void changeThemeAsGuest() {...} {code} Furthermore, @LoginAs should also be defaultable for all tests on the class itself: {code} @LoginAs("admin", "admin") public class MyTest { @Deployment @OverProtocol("Authenticated Servlet") public static WebArchive createDeployment() {...} @Test public void changeThemeAsAdmin() {...} @Test public void changeImportAsAdmin() {...} ... } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012