[cdi-dev] [JBoss JIRA] (CDI-157) Enabling/Disabling Extensions

Fri Sep 14 11:36:32 EDT 2012

    [ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718719#comment-12718719 ] 

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 ...

> Enabling/Disabling Extensions
> -----------------------------
>
>                 Key: CDI-157
>                 URL: https://issues.jboss.org/browse/CDI-157
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>             Fix For: 1.1 (Proposed)
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira