[cdi-dev] [JBoss JIRA] (CDI-453) Support for external interceptor configuration

[Romain Manni-Bucau (JIRA)]

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

Romain Manni-Bucau commented on CDI-453:
----------------------------------------

+1

snice most of servers consider it as global by default we should consider having it as default and allowing only to restrict an interceptor to a bean archive (in <interceptor /> we can add an attribute restricted=true|false)

> Support for external interceptor configuration
> ----------------------------------------------
>
>                 Key: CDI-453
>                 URL: https://issues.jboss.org/browse/CDI-453
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Interceptors, Java EE integration, Java SE Integration
>    Affects Versions: 1.2.Final
>            Reporter: John Ament
>            Priority: Minor
>
> Currently, there is no way to flag that an interceptor should be globally enabled/disabled within an archive/application.
> Say that I have a common JAR with some interceptor annotations on various beans within it.  This JAR has two targetted runtimes, one in a servlet/app server runtime where in one interceptor should be enabled and another disabled.  This same JAR is also used within a standalone (SE) batch program where the first interceptor is off and the second is on.
> In this case, I need a way to specify that an interceptor is on, without changing the deployed bean archive.  I can currently alleviate this through maven shading, but would prefer not to since it tightly couples the archive to the way consumers use it.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)