[
https://issues.jboss.org/browse/ARQ-1991?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on ARQ-1991:
------------------------------------
I would expect that they get processed per deployment as each
deployment archive is run independently at the unit level.
I would have expected the same, and I would assume the weld-core test suite would see a
lot of strange behavior of that was not the case... Could you provide an example of this?
Weld EE embedded container leaks extension configuration
--------------------------------------------------------
Key: ARQ-1991
URL:
https://issues.jboss.org/browse/ARQ-1991
Project: Arquillian
Issue Type: Bug
Components: Weld Containers
Affects Versions: weld_1.0.0.CR9
Reporter: John Ament
I have a maven project that leverages arquillian tests for multiple unit cases. One for
validators and another for DeltaSpike Data module.
The DeltaSpike Data module runs first, followed by the validator one (just happens to be
that order, no specific required order). The validator one includes a class deactivator
extension that disables an extension on boot. The data module one didn't have this.
We began seeing that the data test would pass but the validator suddenly fail. Adding our
deactivator to the data module test caused the validator test to suddenly work (this was
great).
It appears that the CDI extensions provided by the archive are only processed once, I
would expect that they get processed per deployment as each deployment archive is run
independently at the unit level.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)