[
https://issues.jboss.org/browse/CDI-48?page=com.atlassian.jira.plugin.sys...
]
Stuart Douglas updated CDI-48:
------------------------------
Summary: Global Interceptor/Decorator ordering (was: Global interceptor
ordering)
Description:
Currently interceptor/decorator ordering is specified on a per bean archive level. In the
majority of cases the correct ordering is the same for every BDA in the application, so
this violates DRY and opens the door to nasty bugs due to different ordering per module if
beans.xml files get out of sync.
We should look at allowing the user to define interceptor and decorator ordering once per
app and have this applied to all modules in the deployment.
was:
Currently interceptor ordering is specified on a per bean archive level. In the majority
of cases the correct ordering is the same for every BDA in the application, so this
violates DRY and opens the door to nasty bugs due to different ordering per module if
beans.xml files get out of sync.
We should look at allowing the user to define interceptor ordering once per app and have
this applied to all modules in the deployment.
Global Interceptor/Decorator ordering
-------------------------------------
Key: CDI-48
URL:
https://issues.jboss.org/browse/CDI-48
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Stuart Douglas
Currently interceptor/decorator ordering is specified on a per bean archive level. In the
majority of cases the correct ordering is the same for every BDA in the application, so
this violates DRY and opens the door to nasty bugs due to different ordering per module if
beans.xml files get out of sync.
We should look at allowing the user to define interceptor and decorator ordering once per
app and have this applied to all modules in the deployment.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira