Since CDI 1.1 you can enable an interceptor, decorator or alternative globally. This can be done either using the @Priority annotation or by an extension.

Jozef

On 08/22/2014 01:21 PM, John D. Ament wrote:
@Romain

I'm inclined to believe that.  Either way I just created https://issues.jboss.org/browse/CDI-453 so that none of us lose track of it.

John


On Fri, Aug 22, 2014 at 7:05 AM, Romain Manni-Bucau <rmannibucau@gmail.com> wrote:
Hi John, from spec point of view Jozef is right but I think it is
important to mention that most of servers supports it otherwise it is
hardly usable (using lib would be a nightmare).


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-08-22 11:10 GMT+02:00 Jozef Hartinger <jharting@redhat.com>:
> Hi John,
>
> no, the interceptor will only be enabled in war's WEB-INF/classes. Other
> JARs need to enable the interceptor in their beans.xml file to use it.
>
> Jozef
>
>
> On 08/21/2014 08:43 PM, John D. Ament wrote:
>
> Hi,
>
> Let's suppose I'm deploying a WAR file w/ multiple JAR files.  The WAR has a
> beans.xml w/ interceptors defined in it.  The JARs each have beans.xml, but
> no interceptors defined within them.
>
> Should the interceptors in the WAR apply to all of the JAR files?
>
> Thanks,
>
> John
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev