August 2010 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-217) Servlet 2.5 Protocol should support Application WebArchives

by Aslak Knutsen (JIRA)

Servlet 2.5 Protocol should support Application WebArchives ----------------------------------------------------------- Key: ARQ-217 URL: https://jira.jboss.org/browse/ARQ-217 Project: Arquillian Issue Type: Bug Reporter: Aslak Knutsen Currently when using the Servlet 2.5 for EE 5 containers, the Protocol packager will throw an Exception if you try to deploy a WebArchive. It does not support web.xml merging. Use the Descriptors library to append the required Servlet/Mappings. -- 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, 9 months

1
7
0 / 0

[JBoss JIRA] Created: (ARQ-168) Use Bean Validation on container configuration properties

by Dan Allen (JIRA)

Use Bean Validation on container configuration properties --------------------------------------------------------- Key: ARQ-168 URL: https://jira.jboss.org/browse/ARQ-168 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen The container needs to ensure that the user has supplied sane configuration values, or else risk blowing up in weird and unpredictable ways. Rather than doing these laborious checks manually (and possibly only partially), Bean Validation should be used to enforce the values fall with a value range or adhere to a required syntax. -- 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, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (ARQ-259) Provide xsd for all containers and for core

by Pete Muir (JIRA)

Provide xsd for all containers and for core ------------------------------------------- Key: ARQ-259 URL: https://jira.jboss.org/browse/ARQ-259 Project: Arquillian Issue Type: Task Components: Configuration Affects Versions: 1.0.0.Alpha3 Reporter: Pete Muir Priority: Critical This will be a major usability improvement -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-171) ServletMethodExecutor should get context path from container

by Dan Allen (JIRA)

ServletMethodExecutor should get context path from container ------------------------------------------------------------ Key: ARQ-171 URL: https://jira.jboss.org/browse/ARQ-171 Project: Arquillian Issue Type: Bug Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen While working on the JSR 88 container implementation, I noticed that ServletMethodExecutor is using the hard-coded context path "/test" to communicate with the application to invoke the ArquillianServletRunner. I think that the context path is something that the container implementation should be passing to the ServletMethodExecutor in the deploy() method. This assumption poses a particular problem in the JSR 88 container. When a WAR is deployed using JSR 88, the module is assigned a random name, and hence a random context path. Since there is no way to override the context path "/test" used by the ServletMethodExecutor, it fails to communicate with the server. The ServletMethodExecutor constructor should be changed to take the context path as the second parameter. All the container implementations will need to be updated accordingly. -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-153) Protocol configuration element should be separate from Container

by Aslak Knutsen (JIRA)

Protocol configuration element should be separate from Container ---------------------------------------------------------------- Key: ARQ-153 URL: https://jira.jboss.org/browse/ARQ-153 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen A Contianer should be able to run with any of the support Protocols for communication with TestCase running inside the container. This needs to be configurable in a common way. Currently Servlet Protocol configuration is stuck in the specific Containers who use it, this needs to be extracted. e.g. {code:XML} <arquillian xmlns="http://jboss.com/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jboss="urn:arq:org.jboss.arquillian.jbossas.remote60" xmlns:servlet="urn:arq:org.jboss.arquillian.protocol.servlet" xmlns:jmx="urn:arq:org.jboss.arquillian.protocol.jmx" xmlns:jndi="urn:arq:org.jboss.arquillian.jndi"> <jboss:container id="jbossTest"> <localDeploymentBindAddress>my.domain</localDeploymentBindAddress> <servlet:protocol> <remoteServerAddress>remote.server</remoteServerAddress> <remoteServerHttpPort>8181</remoteServerHttpPort> </servlet:protocol> <jndi:protocol>  <javaNamingProviderUrl>jnp://remote.server:1099</javaNamingProviderUrl> <javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial> <javaNamingFactoryUrlPkgs>org.jboss.naming\:org.jnp.interfaces</javaNamingFactoryUrlPkgs> </jndi:protocol> </jboss:container> <jboss:container id="jbossStage"> <localDeploymentBindAddress>my.domain</localDeploymentBindAddress> <jmx:protocol> <serviceUrl>service:jmx:rmi:///jndi/rmi://localhost:1099/</serviceUrl> </jmx:protocol> <jndi:protocol> <javaNamingProviderUrl>jnp://remote.server:1099</javaNamingProviderUrl> <javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial> <javaNamingFactoryUrlPkgs>org.jboss.naming\:org.jnp.interfaces</javaNamingFactoryUrlPkgs> </jndi:protocol> </jboss:container> </arquillian> {code} -- 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, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-152) Support multiple container configurations for same container type

by Aslak Knutsen (JIRA)

Support multiple container configurations for same container type ----------------------------------------------------------------- Key: ARQ-152 URL: https://jira.jboss.org/browse/ARQ-152 Project: Arquillian Issue Type: Feature Request Components: Configuration Reporter: Aslak Knutsen Configuration need to support multiple container configurations for the same container type with a runtime 'flag' for switching configuration. UseCase: Different configuration for test/stage servers. e.g. {code:XML} <arquillian xmlns="http://jboss.com/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jboss="urn:arq:org.jboss.arquillian.jbossas.remote60"> <jboss:container id="jbossTest"> <localDeploymentBindAddress>my.domain</localDeploymentBindAddress> <remoteServerAddress>remote.test.server</remoteServerAddress> <remoteServerHttpPort>8080</remoteServerHttpPort> </jboss:container> <jboss:container id="jbossStage"> <localDeploymentBindAddress>my.domain</localDeploymentBindAddress> <remoteServerAddress>remote.stage.server</remoteServerAddress> <remoteServerHttpPort>8181</remoteServerHttpPort> </jboss:container> </arquillian> {code} -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-110) RunMode Local should reuse protocol-local

by Aslak Knutsen (JIRA)

RunMode Local should reuse protocol-local ----------------------------------------- Key: ARQ-110 URL: https://jira.jboss.org/jira/browse/ARQ-110 Project: Arquillian Issue Type: Task Reporter: Aslak Knutsen Currently the RunMode Local handler has it's own v. of the LocalMethodExecutor. The same code should be shared between the standalone containers(weld, openwebbeans, openejb...) options: - remove protocol-local and replace it with a class in impl? - remove protocol-local and replace it with a class in spi? - make impl depend on protocol-local ? -- 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

14 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (ARQ-158) Replace method arguments with toString instead of Class

by Aslak Knutsen (JIRA)

Replace method arguments with toString instead of Class ------------------------------------------------------- Key: ARQ-158 URL: https://jira.jboss.org/browse/ARQ-158 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen When using Argument injection in TestNG, TestNG tries to write out the values as part of the Report after all contexts are closed. In Alpha-2 we replace all arguments with Class after the test is executed. Replace the arguments with toString instead, this way the user can control what is written. -- 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, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (ARQ-192) Install OSGi bundles in memory

by Thomas Diesler (JIRA)

Install OSGi bundles in memory ------------------------------ Key: ARQ-192 URL: https://jira.jboss.org/browse/ARQ-192 Project: Arquillian Issue Type: Task Reporter: Thomas Diesler Currently the OSGiDeploymentPackager transforms a JavaArchive into a VF private VirtualFile toVirtualFile(Archive<?> archive) throws IOException, MalformedURLException { // [TODO] Can this be done in memory? ZipExporter exporter = archive.as(ZipExporter.class); String archiveName = archive.getName(); int dotIndex = archiveName.lastIndexOf("."); if (dotIndex > 0) archiveName = archiveName.substring(0, dotIndex); File target = File.createTempFile(archiveName + "-", ".jar"); exporter.exportZip(target, true); target.deleteOnExit(); return AbstractVFS.getRoot(target.toURI().toURL()); } We should be able to install the Archive directly and in-memory -- 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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (ARQ-227) Support Deployment exception assert

by Aslak Knutsen (JIRA)

Support Deployment exception assert ----------------------------------- Key: ARQ-227 URL: https://jira.jboss.org/browse/ARQ-227 Project: Arquillian Issue Type: Feature Request Components: Test Harness Integration Reporter: Aslak Knutsen For container / deployer / framework dev it is useful to be able to Assert on Deployment related issues. e.g. http://arquillian.pastebin.com/hPCh8yQd -- 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, 9 months

1
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2010