[ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-157: -------------------------- Description: Typically an extension class is packaged in a jar, along with a META-INF/services/javax.enterprise.inject.spi.Extension file which enables it. However, this means that an application, or another extension, has no way of disabling extensions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-157: ------------------------------- [~struberg] [~lightguard] can we use the Deactivatable approach from DeltaSpike here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-157: ----------------------------------- Of course we could, but what would be the additional benefit? The isActivated() in Deltaspike must get implemented in each and every Extension. Otoh it also allows fine grained control if a single Extensions implements multiple Features. Another option would be to add a section to beans.xml in which case the container would then just skip registering the Extension. With the 'ordering' of CDI-18 in place we could later override the disabling again. Just an idea ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-157: ----------------------------------- Proposal: # Add a way to register Extensions via beans.xml, e.g <extensions><class enabled="true" ordinal="17">... # Treat any Extension registered via META-INF/services/... as registered with enabled="true" and an ordinal="1" That would allow users to just define another beans.xml with a highter ordinal where he can disable the Extension. Containers must pickup all Extensions registered via META-INF/Services plus all Extensions registered via beans.xml. For each Extension class only the entry with the highest ordinal counts. In case this evaluates to enabled="true" the CDI Container shall instantiate and enable the Extension, otherwise it shall get skipped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-157: ----------------------------------- for each Extension class there will only be a single Extension loaded. The highest ordinal defines the configuration. In our case now it's only enabled = true or false. But I could even imagine to introduce parameters for initializing Extensions in beans.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira