[jboss-jira] [JBoss JIRA] Commented: (AS7-1042) Adding interceptors with the same priority leads to non-deterministic behaviour

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609567#comment-12609567 ] 

Stuart Douglas commented on AS7-1042:
-------------------------------------

Interceptor order is completely deterministic.

The sort used by the interceptors is guaranteed to be stable, so the order that user interceptors are added is the order they are executed, and the code that adds them is careful to add in the correct order. 

Instantiators and injectors should be order agnostic, if there is a need for a specific ordering it should be expressed via a new entry in the InterceptorOrder class.

In this case someone entering the wrong priority in InterceptorOrder caused a bug, other that writing a unit test that checks that the values are different via reflection I don't really see what else you can do.

> Adding interceptors with the same priority leads to non-deterministic behaviour
> -------------------------------------------------------------------------------
>
>                 Key: AS7-1042
>                 URL: https://issues.jboss.org/browse/AS7-1042
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EE
>            Reporter: Carlo de Wolf
>            Assignee: Carlo de Wolf
>            Priority: Blocker
>             Fix For: 7.0.0.CR1
>
>
> {code:java}
> public static final int SINGLETON_CONTAINER_MANAGED_CONCURRENCY_INTERCEPTOR = 0x800;
> public static final int USER_INTERCEPTORS = 0x800;
> {code}
> The order of execution between CONCURRENCY and USER is no longer guaranteed.
> The EE framework must detect such a setup and fail.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira