[
https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.s...
]
Pëtr Andreev commented on ARQ-1618:
-----------------------------------
@Aslak: are there (m)any other issues preventing the Brute Force Extension to be
incorporated into the ARQ master? I find that this extension is great enhancement saving
lot of development time.
Transaction extension configuration is not loaded early enough when
working with ArquillianSuiteExtension
---------------------------------------------------------------------------------------------------------
Key: ARQ-1618
URL:
https://issues.jboss.org/browse/ARQ-1618
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Transaction
Affects Versions: transaction_1.0.0.Final
Environment: Win7,CentOS
Jboss7, Wildfly8
Reporter: Pëtr Andreev
Priority: Minor
The TransactionConfigurationProducer loads an extension configuration on demand using the
BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force
Arquillian Suite Extension is in play, since the Suite Extension interferes the test case
bootstrap process and enforces early usage of ARQ components.
As a suggestion for TX-ext to support such a constellation the configuration loading of
transaction extension can be moved right into the phase where ConfigurationRegistrar loads
configurations and notifies observers about available ArquillianDescriptors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira