April 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-415) Use Seam Solder instead of Weld Extensions

by Hendy Irawan (JIRA)

Use Seam Solder instead of Weld Extensions ------------------------------------------ Key: ARQ-415 URL: https://issues.jboss.org/browse/ARQ-415 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Examples Affects Versions: 1.0.0.Alpha5 Reporter: Hendy Irawan Use Seam Solder instead of Weld Extensions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (ARQ-700) Properties in arqullian.xml should handle new lines

by Hardy Ferentschik (Created) (JIRA)

Properties in arqullian.xml should handle new lines ---------------------------------------------------- Key: ARQ-700 URL: https://issues.jboss.org/browse/ARQ-700 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 1.0.0.CR6 Reporter: Hardy Ferentschik When trying to add _javaVmArguments_ to _arquillian.xml_ in order to debug the container new lines in the property will cause the container start to fail. For example, the following works: {code} <arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> <engine> <property name="deploymentExportPath">target/</property> </engine> <container qualifier="jboss" default="true"> <protocol type="jmx-as7"> <property name="executionType">REMOTE</property> </protocol> <configuration> <property name="jbossHome">target/jboss-as-7.1.0.Beta1</property> <property name="javaVmArguments">-Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=y -Xmx512m -XX:MaxPermSize=128m</property> </configuration> </container> </arquillian> {code} whereas this fails: {code} <arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> <engine> <property name="deploymentExportPath">target/</property> </engine> <container qualifier="jboss" default="true"> <protocol type="jmx-as7"> <property name="executionType">REMOTE</property> </protocol> <configuration> <property name="jbossHome">target/jboss-as-7.1.0.Beta1</property> <property name="javaVmArguments"> -Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=y -Xmx512m -XX:MaxPermSize=128m </property> </configuration> </container> </arquillian> {code} given that often people use auto-formatting for xml the parser should take care of this and trim the configuration value. Also the resulting exception for the case where the value is on a new line is very confusing: {noformat} org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:180) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:78) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 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 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.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 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.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 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.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:71) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:199) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [30] s at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:176) ... 65 more {noformat} -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-74) Base test deployment on project in which test is run

by Pete Muir (JIRA)

Base test deployment on project in which test is run ---------------------------------------------------- Key: ARQ-74 URL: https://jira.jboss.org/jira/browse/ARQ-74 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir A common testing scenario will be to deploy the artifact generated by the current project, and run tests against it. For example, say my project was building a war, I want to be able to deploy that war, inserting the test case and any beans into the deployment, and have my tests run. In this case the deep control of the classpath through shrinkwrap is getting in the way. -- 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

12 years, 2 months

3
8
0 / 0

[JBoss JIRA] (ARQ-865) Allow managerUrl (or manager contextPath) to be configured in remote 6 container

by Dan Allen (JIRA)

Dan Allen created ARQ-865: ----------------------------- Summary: Allow managerUrl (or manager contextPath) to be configured in remote 6 container Key: ARQ-865 URL: https://issues.jboss.org/browse/ARQ-865 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: tomcat_1.0.0.CR3 Reporter: Dan Allen Tomcat 7 changed the context path for the manager apps. For the purpose of what the Arquillian adapter uses, the context path changed from /manager to /manager/text. Unfortunately, the tomcat adapter does not provide a way to configure the context path of the manager url. It builds it automatically as follows: {code} protected URL createManagerUrl() throws MalformedURLException { final String template = "http://%s:%d/manager"; return new URL(String.format(template, bindAddress, bindHttpPort)); } {code} At a minimum, we should add a new property "managerContextPath" and honor that in this method. Better would be to also allow the managerUrl to be overridden entirely. This currently does not work because 1. arquillian cannot convert a configuration property to a URL 2. even if it did, the value is overridden in the validate() method anyway This fix will allow the Tomcat 6 remote adapter to work with Tomcat 7. Side note: The user should also be advised that it is necessary to include the JMX startup properties when starting Tomcat 7. -Dcom.sun.management.jmxremote.port=8089 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] (ARQ-898) Improve the readability of the name of the archive file exported by the ArchiveDeploymentExporter

by Dan Allen (JIRA)

Dan Allen created ARQ-898: ----------------------------- Summary: Improve the readability of the name of the archive file exported by the ArchiveDeploymentExporter Key: ARQ-898 URL: https://issues.jboss.org/browse/ARQ-898 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.Final Reporter: Dan Allen Priority: Minor The archive file that is exported by the ArchiveDeploymentExporter is very oddly named under typical circumstances. _DEFAULT___DEFAULT__test.war We need to find some way to make this more friendly to the developer. For one, we could use hyphens to separate the segments so that they don't stack: _DEFAULT_-_DEFAULT_-test.war Another option is to strip the underscores if the name is _DEFAULT_: DEFAULT-DEFAULT-test.war That at least looks presentable. We should also document somewhere when the _DEFAULT_ name gets replaced with a custom one (I can't figure it out). -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] (ARQ-896) Reformat to use new jboss-common formatting rules

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-896: --------------------------------- Summary: Reformat to use new jboss-common formatting rules Key: ARQ-896 URL: https://issues.jboss.org/browse/ARQ-896 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Final Reporter: Aslak Knutsen Fix For: 1.1.0.Beta1 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-160) Improve Exception messages / handling

by Aslak Knutsen (JIRA)

Improve Exception messages / handling ------------------------------------- Key: ARQ-160 URL: https://jira.jboss.org/browse/ARQ-160 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen We should create an Exception message id set linking to wiki articles/faq about the specific error case. This will help on the user experience and exposure of jboss.org -- 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

12 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-224) Create Wiki entries for every Error Message id

by Aslak Knutsen (JIRA)

Create Wiki entries for every Error Message id ---------------------------------------------- Key: ARQ-224 URL: https://jira.jboss.org/browse/ARQ-224 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Every Exception ID Arquillian defines should be mapped to a open wiki page where we can add description about the exception, why and how to fix it 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

12 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-232) Redesign Servlet protocol to be more human friendly

by Aslak Knutsen (JIRA)

Redesign Servlet protocol to be more human friendly --------------------------------------------------- Key: ARQ-232 URL: https://jira.jboss.org/browse/ARQ-232 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Reporter: Aslak Knutsen Priority: Minor We should redesign the Servlet communication protocol to be more Rest api like. This will make it easier for humans to execute tests outside of the Arquillian Client and opens for other clients to communicate with the test. http://arquillian.pastebin.com/XHsfaycJ Add support for html output -- 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

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-442) Change Examples modules to a container sanity test suite

by Aslak Knutsen (JIRA)

Change Examples modules to a container sanity test suite -------------------------------------------------------- Key: ARQ-442 URL: https://issues.jboss.org/browse/ARQ-442 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta1 Reporter: Aslak Knutsen The current examples modules should be recreated as a sanity test suite for the containers. Currently all containers have their own simple tests for validating the functionality. These container tests should be merged with the examples and created as a test suite. The test suite needs to be split up by package / module based on EE v / technology to support all containers(easy maven filtering). The containers should depend on this test suite and not the other way around. todo: research how to include a external module as a test suite for a module. (copy-dependencies / extract ? / container config etc) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2012