-
1. Weld leakage into ARQ subsystem
alesj Feb 7, 2011 10:53 AM (in response to thomas.diesler)We (Stuart and me) already discussed this, and he's aware that this needs to be fixed.
I think a simple / basic idea is to have SetupActions as part of deployment's attachments,
where each sub-system properly adds them to the underlying deployment.
But I'll let you two discuss the details. :-)
-
2. Weld leakage into ARQ subsystem
swd847 Feb 7, 2011 3:08 PM (in response to thomas.diesler)There are two weld related things in the subsystem, both of them are temporary.
At the moment there is no 'proper' way to tell when a deployment is finished, so I wait on the weld service to come up to make sure that the deployment is in a usable state before the tests run.
Also as Ales mentioned above I am also planning on moving the setup actions stuff out of Arquillian and into the appropriate subsystem.
Stuart
-
3. Weld leakage into ARQ subsystem
swd847 Feb 8, 2011 6:40 PM (in response to swd847)I have a fix here: https://github.com/stuartwdouglas/jboss-as/tree/arqFix
I will try and get it merged when master is unfrozen
-
4. Weld leakage into ARQ subsystem
thomas.diesler Feb 9, 2011 8:33 AM (in response to swd847)Thanks, I pull it in here: https://github.com/jbosgi/jboss-as/commit/aedf9fbd62cdb9f9d456ca01061023df2b9a567c
I still like to discuss what needs to change in ARQ so that your use case is supported.
ARQ allready supports @BeforeClass/@AfterClass and @Before/@After. Is it not possible to put the logic in the test? The ContextManager could be injected by a TestEnricher. Does ARQ need a notion of SetupAction?
Let me ping Aslak about this.