Alex Soto created ARQ-2053:
------------------------------
Summary: Allow Arquillian Core to define a way to execute registration of
extensions in order
Key: ARQ-2053
URL:
https://issues.jboss.org/browse/ARQ-2053
Project: Arquillian
Issue Type: Bug
Reporter: Alex Soto
Priority: Minor
With Arquillian Extensions you are able to override a service that was previously
registered by Arquillian Core or by other extensions.
The problem is that if if there two extensions that override the same service, it will
depend on the order of the registration of the extension that will define which version of
the service will be the one used at the end.
To avoid this problem this problem the best way would be to be able to set a priority in
extension registry so you can set which one is going to be the last one.
The best none invasive approach we have found is using an annotation to set the order
where the highest number is the last one to execute. In case of not defining a an
annotation, the default order number will be 0.
So as an example an extension could be defined as:
{code:java}
@Precendence(100)
public class MyExtension implements LoadableExtension {}
{code}
The higher value of precedence the sooner it will be registered. This means that to ensure
that your extension is registered last, it needs a negative value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)