January 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-167) Support @EJB.mappedName for TestClass injection

by Aslak Knutsen (JIRA)

Support @EJB.mappedName for TestClass injection ----------------------------------------------- Key: ARQ-167 URL: https://jira.jboss.org/browse/ARQ-167 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen We should support letting the user set the mappedName on the injection in the test case to avoid having to follow our naming standards. (until we can do it more reliable, https://jira.jboss.org/browse/ARQ-77) Needs to document the potential jndi naming changes between Embedded EJB containers and Remote Containers(packaging).. -- 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, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (ARQ-319) Allow container START_TIME to be configurable in arquillian.xml

by Jim Crossley (JIRA)

Allow container START_TIME to be configurable in arquillian.xml --------------------------------------------------------------- Key: ARQ-319 URL: https://jira.jboss.org/browse/ARQ-319 Project: Arquillian Issue Type: Feature Request Reporter: Jim Crossley Priority: Minor It'd be nice to be able to extend that start_time from 120s to something longer on a busy CI server. The jbossas.startup.timeout sys prop is nice, but having it in arquillian.xml would be more convenient. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-356) JBoss AS Managed does not allow to set RMI port used for deployment. Forces users to use 1099

by Aslak Knutsen (JIRA)

JBoss AS Managed does not allow to set RMI port used for deployment. Forces users to use 1099 --------------------------------------------------------------------------------------------- Key: ARQ-356 URL: https://issues.jboss.org/browse/ARQ-356 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen Priority: Minor The RMIPort has to be set specifically on the ServerManager for it to be able to connect to anything else then the default: 1099. Open up for RMIPort configuration in arquillian.xml for the JBoss Managed containers. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (ARQ-218) ServiceLoader should support Default implementations

by Aslak Knutsen (JIRA)

ServiceLoader should support Default implementations ---------------------------------------------------- Key: ARQ-218 URL: https://jira.jboss.org/browse/ARQ-218 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen The ServiceLoader.onlyOne fails if no implementation found. In some cases Arquillian will provide a default implementation but it should still be overridable from the outside. Add onlyOne(Interface spi, Class defaultImpl) -- 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, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (ARQ-352) ArquillianDescriptor should support configuration of extensions

by Karel Piwko (JIRA)

ArquillianDescriptor should support configuration of extensions --------------------------------------------------------------- Key: ARQ-352 URL: https://issues.jboss.org/browse/ARQ-352 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Beta1 ArquillianDescriptor should provide a way how to configure extensions. This should be done in the same manner as for containers, protocols and groups. E.g. <?xml version="1.0" encoding="UTF-8" standalone="no"?> <arquillian> <extension qualifier="selenium"> <configuration> <property name="speed">5000</property> </configuration> </extension> </arquillian> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-304) String based properties cannot be loaded through System properties

by Karel Piwko (JIRA)

String based properties cannot be loaded through System properties ------------------------------------------------------------------ Key: ARQ-304 URL: https://jira.jboss.org/browse/ARQ-304 Project: Arquillian Issue Type: Bug Components: Extension - Selenium Reporter: Karel Piwko Assignee: Karel Piwko Priority: Minor Fix For: 1.0.0.Beta1 Selenium cannot load String based properties in configuration due to missing handler for String based properties. Caused by: java.lang.IllegalArgumentException: Unable to convert value org.openqa.selenium.firefox.FirefoxDriverto a class: java.lang.String at org.jboss.arquillian.selenium.SeleniumExtensionConfiguration$SystemPropertyConfiguration.convert(SeleniumExtensionConfiguration.java:439) at org.jboss.arquillian.selenium.SeleniumExtensionConfiguration$SystemPropertyConfiguration.get(SeleniumExtensionConfiguration.java:387) at org.jboss.arquillian.selenium.SeleniumExtensionConfiguration.getWebdriverImplementation(SeleniumExtensionConfiguration.java:346) at org.jboss.arquillian.selenium.instantiator.WebDriverInstantiator.create(WebDriverInstantiator.java:62) at org.jboss.arquillian.selenium.instantiator.WebDriverInstantiator.create(WebDriverInstantiator.java:38) at org.jboss.arquillian.selenium.event.SeleniumStartupHandler.prepareContext(SeleniumStartupHandler.java:86) at org.jboss.arquillian.selenium.event.SeleniumStartupHandler.callback(SeleniumStartupHandler.java:60) at org.jboss.arquillian.selenium.event.SeleniumStartupHandler.callback(SeleniumStartupHandler.java:48) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-316) more complete support for servlet 2.5

by Dan Allen (JIRA)

more complete support for servlet 2.5 ------------------------------------- Key: ARQ-316 URL: https://jira.jboss.org/browse/ARQ-316 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 Provide a more complete packaging implementation for in-container testing over the Servlet 2.5 protocol. Specifically, support all three archive types in @Deployment method: WAR, JAR and EAR. -- 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, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (ARQ-196) Research how Arquillian can support controlling multiple Containers

by Aslak Knutsen (JIRA)

Research how Arquillian can support controlling multiple Containers ------------------------------------------------------------------- Key: ARQ-196 URL: https://jira.jboss.org/browse/ARQ-196 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Priority: Minor For clustering and OSGi distributed test controlling the lifecycle of multiple Containers at the same time is needed. The same can be used for remoting between two containers etc. The Deployer API should then probably support deploying to a specific instance. -- 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, 10 months

1
7
0 / 0

[JBoss JIRA] Created: (ARQ-349) Create a Protocol processor SPI for modifying the Protocol create final deployment

by Aslak Knutsen (JIRA)

Create a Protocol processor SPI for modifying the Protocol create final deployment ---------------------------------------------------------------------------------- Key: ARQ-349 URL: https://issues.jboss.org/browse/ARQ-349 Project: Arquillian Issue Type: Feature Request Components: Packaging Enricher SPI Reporter: Aslak Knutsen In some cases we need to modify the Protocol generated Deployment. In the case of CDI, it's BeanManagers are hierarchical, a BeanManager created for a ejb-jar in a ear is not visible to a war unless the war also contains a beans.xml. When using the Servlet Protocol, a war is added without a beans.xml since the protocol it self is unaware of CDI, and Beans are never injected into the testcase. DeploymentProcessor.process(TestClass relevant class, TestDeployment auxAndApplicationArchives, Archive<?> finalDeployment); https://issues.jboss.org/browse/WELD-709 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-283) Support loading of configuration for Arquillian-Selenium

by Karel Piwko (JIRA)

Support loading of configuration for Arquillian-Selenium -------------------------------------------------------- Key: ARQ-283 URL: https://jira.jboss.org/browse/ARQ-283 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Beta1 At the moment, Arquillian Selenium extension does not support loading configuration through arquillian.xml, but only through System properties. Align configuration with the XML based one, developed within ARQ-215 and find a way how to leave System.properties configuration intact. -- 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, 10 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2011