[JBoss JIRA] Updated: (CDI-2) Interceptor bindings defined at method level should override those at the class level
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/CDI-2?page=com.atlassian.jira.plugin.syst... ]
Pete Muir updated CDI-2:
------------------------
Fix Version/s: 1.1 (Proposed)
(was: TBD)
> Interceptor bindings defined at method level should override those at the class level
> -------------------------------------------------------------------------------------
>
> Key: CDI-2
> URL: https://issues.jboss.org/browse/CDI-2
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Interceptors
> Affects Versions: 1.0
> Reporter: Pete Muir
> Fix For: 1.1 (Proposed)
>
>
> We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec.
> In section 9.5.2 of the spec:
> If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Updated: (CDI-48) Global Interceptor/Decorator ordering
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/CDI-48?page=com.atlassian.jira.plugin.sys... ]
Pete Muir updated CDI-48:
-------------------------
Fix Version/s: 1.1 (Proposed)
(was: TBD)
> Global Interceptor/Decorator ordering
> -------------------------------------
>
> Key: CDI-48
> URL: https://issues.jboss.org/browse/CDI-48
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Decorators, Interceptors, Packaging and Deployment
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 1.1 (Proposed)
>
>
> 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
13 years, 3 months