Return-Path: X-Original-To: apmail-deltaspike-commits-archive@www.apache.org Delivered-To: apmail-deltaspike-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA6BC18A15 for ; Mon, 17 Aug 2015 02:52:53 +0000 (UTC) Received: (qmail 43019 invoked by uid 500); 17 Aug 2015 02:52:53 -0000 Delivered-To: apmail-deltaspike-commits-archive@deltaspike.apache.org Received: (qmail 42981 invoked by uid 500); 17 Aug 2015 02:52:53 -0000 Mailing-List: contact commits-help@deltaspike.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltaspike.apache.org Delivered-To: mailing list commits@deltaspike.apache.org Received: (qmail 42971 invoked by uid 99); 17 Aug 2015 02:52:53 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 02:52:53 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id B2798AC0354 for ; Mon, 17 Aug 2015 02:52:53 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r962064 - in /websites/staging/deltaspike/trunk/content: ./ documentation/spi.html Date: Mon, 17 Aug 2015 02:52:53 -0000 To: commits@deltaspike.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150817025253.B2798AC0354@hades.apache.org> Author: buildbot Date: Mon Aug 17 02:52:53 2015 New Revision: 962064 Log: Staging update by buildbot for deltaspike Modified: websites/staging/deltaspike/trunk/content/ (props changed) websites/staging/deltaspike/trunk/content/documentation/spi.html Propchange: websites/staging/deltaspike/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Mon Aug 17 02:52:53 2015 @@ -1 +1 @@ -1696186 +1696189 Modified: websites/staging/deltaspike/trunk/content/documentation/spi.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/spi.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/spi.html Mon Aug 17 02:52:53 2015 @@ -336,6 +336,21 @@ as soon as everything is initialized the

A class-deactivator will be resolved from the environment via the default resolvers or via a custom resolver which allows to use any type of configuration-format. (see org.apache.deltaspike.core.api.config.ConfigResolver). The key is the fully qualified name of the interface (org.apache.deltaspike.core.spi.activation.ClassDeactivator).

+
+

Starting with (TBD v1.5.1), Apache DeltaSpike ships a default Class Deactivator. It is designed mostly for testing purposes, but is meant to reduce code overhead +and allow configuration to drive classes to deactivate. It is built upon the ConfigSource paradigm, which allows for configuration based keys to deactivate your +classes. If you’re not using any other ConfigSource, you can simply add entries to META-INF/apache-deltaspike.properties to disable classes at runtime. Here’s an +example configuration

+
+
+
+
org.apache.deltaspike.core.spi.activation.ClassDeactivator=org.apache.deltaspike.core.impl.activation.DefaultClassDeactivator
+deactivate.org.apache.deltaspike.test.core.impl.activation.DeactivatedClass=true
+
+
+
+

By listing the class in the properties file and setting the value to true, the class will be deactivated. This is valid for anything where Boolean.valueOf returns true.

+