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

[Aslak Knutsen (JIRA)]

    [ https://jira.jboss.org/browse/ARQ-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12549092#action_12549092 ] 

Aslak Knutsen commented on ARQ-196:
-----------------------------------

With multiple Containers we should support any number of any type of containers.

e.g. 
Connect and deploy against a JBoss AS 5.1 and a GlassFish 3 in the same run while running the test case in a Weld Embedded container.

To support multiple different Containers we need ClassPath control so the Client libs don't mix. We can open up arquillian.xml with maven artifact style configuration for the Container deps using the new Sonatype Aether lib to fetch them and setup the ClassLoaders.
https://docs.sonatype.org/display/AETHER/Home


We should open up for multiple @Deployment methods on a TestCase with a ID ref to which container to deploy to:

e.g.

@Deployment(MyTestScenario.BACKEND_SYSTEM_1)
public static Archive<?> create() ..

or 

@TargetContainer(MyTestScenario.FRONTEND_SYSTEM_1)
@Deployment
public static Archive<?> create() ..


For the Exposed Deployer API we need the same style of support. (ARQ-195)

e.g.

@ArquillianResource(MyTestScenario.BACKEND_SYSTEM_1)
Deployer backendDeployer;

or

@TargetContainer(MyTestScenario.FRONTEND_SYSTEM_1)
@ArquillianResource
Deployer backendDeployer;

or 

Deployer.deploy(MyTestScenario.BACKEND_SYSTEM_1, archive)


> 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
>             Fix For: 1.1.0.CR1
>
>
> 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