Re: [cdi-dev] [javaee-spec users] Re: About Interceptors's enabling

having @Priority on an interceptor basically disables the 'BDA enablement' and enables 'global enablemant' as per the spec (CDI-18). Since defining an interceptor in beans.xml was originally specifically for 'BDA enablement', I have expected the ordering to only follow the @Priority rules in this case.. But of course this could be made clearer in the spec. Pete, what is your take on this? LieGrue, strub       interceptor chain       defines the position of the interceptor in the interceptor chain       (which is possibly different from (1))       take precedence nor forbids this case. As this case is unspecified       I would consider "calling the interceptor twice" a possible       implementation.         interceptor is enabled. But it still is there only once.                 pop up on SO recently.                 annotated                 twice.                   :-(                   what you would prefer?                   enabling.                   from "5.3 Ordering                   of JSR 318.                   component method, or constructor                   the entire application by                   a priority value, on the                   deployment-specific and are disabled                   have to be                   descriptor beans.xml of the jar.                   meet two cases,                   explicitly if I am not ready                   of whether to need to                   may break/override                   beans.xml explicitly has                   interceptors binding, so, for                   I made a mistake in [2].                   "enable interceptors in                   resposibility?