[
https://issues.jboss.org/browse/AS7-1042?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf commented on AS7-1042:
------------------------------------
This will prove problematic for not only user interceptors, but also instantiators,
injectors and others. Basically on a single priority level one interceptor is allowed,
what happens within (one priority) that interceptor is an implementation detail. User
interceptors need to have a specific order, others like injectors don't. All will use
a weaved interceptor and hide those details.
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