[arquillian-issues] [JBoss JIRA] Issue Comment Edited: (ARQ-336) Inject container references in the test to start/stop containers

[ https://issues.jboss.org/browse/ARQ-336?page=com.atlassian.jira.plugin.sy... ] Karel Piwko edited comment on ARQ-336 at 7/18/11 12:37 PM: ----------------------------------------------------------- We already had a two state logic in Arquillian - RunAs(CLIENT, INCONTAINER) and it was replaced in Alpha5. Couldn't we move this to the class directly? Something like: {code} @ContainerSuiteLifecycle class FooTest { ... } {code} or {code} @ContainerManualLifecycle("jboss1") @ContainerClassLifecycle("jboss2", "jboss3") class Foo2Test { @Deployment @TargetsContainer("jboss1") ... } {code} In XML/XSD, this mapping would correspond rather to an element than attribute, so user can easily provide his own implementation and not depend on suite/class/manual possibilities, similar to protocols. was (Author: kpiwko): We already had a two state logic in Arquillian - RunAs(CLIENT, INCONTAINER) and it was replaced in Alpha5. Couldn't we move this to the class directly? Something like: {code} @ContainerSuiteLifecycle class FooTest { ... } {code} @ContainerManualLifecycle("jboss1") @ContainerClassLifecycle("jboss2", "jboss3") class Foo2Test { @Deployment @TargetsContainer("jboss1") ... } {code} In XML/XSD, this mapping would correspond rather to an element than attribute, so user can easily provide his own implementation and not depend on suite/class/manual possibilities, similar to protocols. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira