[weld-issues] [JBoss JIRA] Commented: (CDI-18) cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives

[ https://jira.jboss.org/browse/CDI-18?page=com.atlassian.jira.plugin.syste... ] Mark Struberg commented on CDI-18: ---------------------------------- This issue originates from the interceptor order problematic as discussed on the EG and weld-dev lists a year ago. One possible solution would be to introduce 'ordinal' and 'enabled' attributes to the <interceptors>, <decorators> and <alternatives> sections like the following example shows: <interceptors ordinal="32"> <class>org.myclass.MyInterceptor3</class> <class>org.myclass.MyOtherInterceptor</class> <class enabled="false">org.myclass.MyFirstInterceptor</class> </interceptors> Where <interceptors> sections with higher ordinals get applied later and thus being more 'important'. So if the default interceptor order you get with a jar doesn't fit your needs, you can still provide a beans.xml containing a fixed one with a higher ordinal. It is also possible to disable interceptors which got switched on by default in a lower prioritized beans.xml section by adding enabled="false". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira