December 2010 - arquillian-issues

[JBoss JIRA] Created: (ARQ-57) JBossAS Remote Containers Depend upon Sun JDK

by Andrew Lee Rubinger (JIRA)

JBossAS Remote Containers Depend upon Sun JDK --------------------------------------------- Key: ARQ-57 URL: https://jira.jboss.org/jira/browse/ARQ-57 Project: Arquillian Issue Type: Bug Components: Jboss Containers Reporter: Andrew Lee Rubinger Assignee: Pete Muir Both the AS 5.1 and 6.0 implementations of JbossRemoteContainer have: import com.sun.net.httpserver.HttpExchange; import com.sun.net.httpserver.HttpHandler; import com.sun.net.httpserver.HttpServer Recommend an external dependency on a safe alternative like apache-httpcomponent's HttpClient or Jetty, ie: http://anonsvn.jboss.org/repos/jbossas/projects/ejb-book/trunk/ch07-rssca... -- 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

13 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (ARQ-345) Arquillian needs to deliver a raw archive to the test container

by David Bosschaert (JIRA)

Arquillian needs to deliver a raw archive to the test container --------------------------------------------------------------- Key: ARQ-345 URL: https://issues.jboss.org/browse/ARQ-345 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Reporter: David Bosschaert In order to support performance tests and deployment testing Arquillian needs to be able to deliver raw archives to the tests being run inside a container. * For performance tests it's important to measure exactly the amount of time a deployment might take and this measurement should not be polluted with the time it takes a client to construct a bundle and the time spent in sending the archive over a socket to the test running in the container. * For deployment tests, the test itself needs to directly exercise the deployment APIs using test archives, it cannot let the Arquillian framework do this. This is currently possible in the OSGiContainerImpl class in the getTestArchive() method https://github.com/jbosgi/arquillian/blob/jbosgi/protocols/osgi/src/main/... however this functionality is currently limited to OSGi deployments only. To be able to implement this properly, Shrinkwrap needs to be capable of running in a module system such as OSGi, so this issue depends on https://issues.jboss.org/browse/SHRINKWRAP-242 . -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-31) Jboss AS Arquillian Deployer

by Aslak (JIRA)

Jboss AS Arquillian Deployer ---------------------------- Key: ARQ-31 URL: https://jira.jboss.org/jira/browse/ARQ-31 Project: Arquillian Issue Type: Feature Request Reporter: Aslak It could be interesting to have a Arquillian Deployer in AS. scanning for *-tests.jar(Maven style) files and deploying them wrapped as a runnable testsuite/testcase via ie jmx. this would basically bypass the 'client' side of Arquillian and run directly on the server. -- 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

13 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (ARQ-198) Install bundle from maven dependencies

by Thomas Diesler (JIRA)

Install bundle from maven dependencies -------------------------------------- Key: ARQ-198 URL: https://jira.jboss.org/browse/ARQ-198 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Reporter: Thomas Diesler * Another interesting feature would be the installation of bundles that are declared as dependencies in the maven pom.xml. Let's say in the pom.xml you have the following dependency: <dependency> <groupId>org.apache.felix</groupId> <artifactId>org.apache.felix.configadmin</artifactId> <version>${configadmin.version}</version> </dependency> then it would be great if you could install that bundle simply through some installBundle("org.apache.felix", "org.apache.felix.configadmin") API which would infer the version from the maven context. Both Pax Exam and Apache ServiceMix testing have this feature and it makes integration with the maven buildsystem really easy. -- 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, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (ARQ-194) Support multiple bundle deployments

by Thomas Diesler (JIRA)

Support multiple bundle deployments ----------------------------------- Key: ARQ-194 URL: https://jira.jboss.org/browse/ARQ-194 Project: Arquillian Issue Type: Feature Request Components: OSGi Integration Reporter: Thomas Diesler Currently a single test bundle is installed from the client side test runner. We should be able to install an arbitrary number of bundles as part of the test method execution -- 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, 7 months

2
12
0 / 0

[JBoss JIRA] Created: (ARQ-195) Expose a Deployer API to the TestCase

by Aslak Knutsen (JIRA)

Expose a Deployer API to the TestCase ------------------------------------- Key: ARQ-195 URL: https://jira.jboss.org/browse/ARQ-195 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Reporter: Aslak Knutsen The TestCase should be able to deploy other deployments as part of it's lifecycle. E.g. - Test the effects of a Deployer - Test lifecycles of Bundles The API needs to be extendable. some Containers might support start/stop as well as deploy/undeploy. -- 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, 7 months

1
5
0 / 0

[JBoss JIRA] Created: (ARQ-216) Extensions should be able to communicate between Client and Container

by Aslak Knutsen (JIRA)

Extensions should be able to communicate between Client and Container --------------------------------------------------------------------- Key: ARQ-216 URL: https://jira.jboss.org/browse/ARQ-216 Project: Arquillian Issue Type: Feature Request Components: Frameworks, Test Protocol SPIs and Implementation Reporter: Aslak Knutsen Arquillian should provide a Communication channel between the Container and Client so extension can push custom data between. This is needed in cases like code coverage where data is collected in container, but reported on on the client side. I think it should be ok to open up the TestRunner Protocols for 'custom' data as well as the TestResults. This means we can piggy back on all the Protocol impls with out much extra work. -- 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, 7 months

1
5
0 / 0

[JBoss JIRA] Created: (ARQ-26) Create a archive repository service for containers not supporting ShrinkWrap directly

by Aslak (JIRA)

Create a archive repository service for containers not supporting ShrinkWrap directly ------------------------------------------------------------------------------------- Key: ARQ-26 URL: https://jira.jboss.org/jira/browse/ARQ-26 Project: Arquillian Issue Type: Task Reporter: Aslak Not all containers will support ShrinkWrap directly. Create a 'Service' or Abstract Deployable Container class to handle Archive<?> to URL mappings. ie, Remote Jboss instances need a http url to deploy. -- 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

13 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (ARQ-66) provide a mechanism for adding library JARs (test dependencies) to the deployment

by Dan Allen (JIRA)

provide a mechanism for adding library JARs (test dependencies) to the deployment --------------------------------------------------------------------------------- Key: ARQ-66 URL: https://jira.jboss.org/jira/browse/ARQ-66 Project: Arquillian Issue Type: Feature Request Components: Core Reporter: Dan Allen Assignee: Pete Muir Fix For: 1.0.0-alpha-1 The requirement to add extra JARs into the deployment is going to surface fairly early on in the adoption of Arquillian. In our examples, we are sticking to APIs in Java EE, but most projects have third-party JARs on which the application depends. Common examples are a logging framework, Apache Commons libraries, Google Collections, Hibernate Search...anything not available in the container. We might need to update the @Deployment signature to support: @Deployment static Set<Archive<?>> x(); Or maybe a seperate @DeploymentDependencies (this could be defined in e.g. a super class) @DeploymentDependencies static Set<Archive<?>> x() We are also going to need to consider providing APIs for resolving Maven dependencies (groupId, artifactId, version) or resolving test dependencies from the Maven pom. We need to be flexible. -- 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

13 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-244) Create a DeployableContainer integration for Google App Engine

by Aslak Knutsen (JIRA)

Create a DeployableContainer integration for Google App Engine -------------------------------------------------------------- Key: ARQ-244 URL: https://jira.jboss.org/browse/ARQ-244 Project: Arquillian Issue Type: Feature Request Components: GAE Containers Reporter: Aslak Knutsen Assignee: Ales Justin Priority: Optional Fix For: 1.0.0.Beta1 Arquillian should support start/stop/deploy and undeploy to a Google App Engine container. -- 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, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2010