You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2014/12/08 21:46:12 UTC

[jira] [Resolved] (DELTASPIKE-349) smart feature-deactivation

     [ https://issues.apache.org/jira/browse/DELTASPIKE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek resolved DELTASPIKE-349.
-----------------------------------------
    Resolution: Later

> smart feature-deactivation
> --------------------------
>
>                 Key: DELTASPIKE-349
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-349
>             Project: DeltaSpike
>          Issue Type: New Feature
>    Affects Versions: 1.0.1
>            Reporter: Gerhard Petracek
>            Assignee: Gerhard Petracek
>
> it should be possible to enable a mode for smart/dynamic feature-deactivation. e.g. if there is no @WindowScoped bean, we can deactivate the classes which handle it (which would get active for every request to do checks,...) -> we get a better out-of-the-box performance optimized for the features used by an application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)