[weld-issues] [JBoss JIRA] (WELD-2009) CDI Interceptor/Decorator order precendence when @Priority used and decorator defined in beans.xml

[Andrew Pielage (JIRA)]

Title: Message Title

Andrew Pielage commented on WELD-2009   Re: CDI Interceptor/Decorator order precendence when @Priority used and decorator defined in beans.xml Having the beans.xml take precedence (option 3 in https://issues.jboss.org/browse/CDI-490) allows you to change the order (or any other configuration) from the descriptor without changing the code. As an example, if you needed to change something, but didn't have access to the entire build chain to recompile the changes, you would be stuck. However, if the beans.xml took precedence, then you could add your changes to the beans.xml file, allowing you to override the annotations in the code and make your required changes. GlassFish and other parts of the spec already follow a similar process: https://docs.oracle.com/cd/E19798-01/821-1750/gihzc/index.html Also, as Martin Kouba stated in CDI-490, this conflict should be logged. Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues