[JBoss JIRA] Created: (ARQ-236) Should be able to configure the Container lifecycle based on the Test events
by Aslak Knutsen (JIRA)
Should be able to configure the Container lifecycle based on the Test events
----------------------------------------------------------------------------
Key: ARQ-236
URL: https://jira.jboss.org/browse/ARQ-236
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak Knutsen
A user should be able to customize how he wants the Container to be controlled.
The default behavior is:
@BeforeSuite -> container.start()
@BeforeClass -> container.deploy()
@AfterClass -> container.undeploy()
@AfterSuite -> container.stop()
Other scenarios are:
- Restart server pr test class
@BeforeClass -> container.start()
@BeforeClass -> container.deploy()
@AfterClass -> container.undeploy()
@AfterClass -> container.stop()
- Redeploy pr test method
@BeforeSuite -> container.start()
@Before -> container.deploy()
@After -> container.undeploy()
@AfterSuite -> container.stop()
- Restart pr test method
@Before -> container.start()
@Before -> container.deploy()
@After -> container.undeploy()
@After -> container.stop()
This could be done by adding a Engine configuration option
e.g.:
engine/containerLifeCycle PrSuite|PrClass|PrMethod
this option would map to different ContextAppenders in the background that does the setup/ordering.
--
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, 1 month
[JBoss JIRA] Created: (ARQ-269) Consolidate the remote host configuration for GlassFish Remote
by Dan Allen (JIRA)
Consolidate the remote host configuration for GlassFish Remote
--------------------------------------------------------------
Key: ARQ-269
URL: https://jira.jboss.org/browse/ARQ-269
Project: Arquillian
Issue Type: Feature Request
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Priority: Minor
Fix For: 1.0.0.Alpha4
In order for the GlassFish Remote container to target a remote host (rather than localhost), two separate properties must be set:
deploymentUri
remoteServerAddress
The deploymentUri should really be an internal setting, dynamically set based on the following two configuration values:
remoteServerAddress
remoteServerAdminPort
This hides the more cryptic deploymentUri value and exposes more user-friendly configuration, less prone to errors.
--
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, 2 months