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 251701089B for ; Mon, 15 Dec 2014 22:31:44 +0000 (UTC) Received: (qmail 67223 invoked by uid 500); 15 Dec 2014 22:31:44 -0000 Delivered-To: apmail-deltaspike-commits-archive@deltaspike.apache.org Received: (qmail 67105 invoked by uid 500); 15 Dec 2014 22:31:44 -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 67010 invoked by uid 99); 15 Dec 2014 22:31:43 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 22:31:43 +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 A9D7AAC08CB for ; Mon, 15 Dec 2014 22:31:43 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r932889 [1/7] - in /websites/staging/deltaspike/trunk/content: ./ documentation/ Date: Mon, 15 Dec 2014 22:31:43 -0000 To: commits@deltaspike.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20141215223143.A9D7AAC08CB@hades.apache.org> Author: buildbot Date: Mon Dec 15 22:31:42 2014 New Revision: 932889 Log: Staging update by buildbot for deltaspike Added: websites/staging/deltaspike/trunk/content/documentation/addons.html websites/staging/deltaspike/trunk/content/documentation/articles.html websites/staging/deltaspike/trunk/content/documentation/cdiimp.html websites/staging/deltaspike/trunk/content/documentation/configure.html websites/staging/deltaspike/trunk/content/documentation/external.html websites/staging/deltaspike/trunk/content/documentation/modules.html websites/staging/deltaspike/trunk/content/documentation/overview.html websites/staging/deltaspike/trunk/content/documentation/snapshots.html Modified: websites/staging/deltaspike/trunk/content/ (props changed) websites/staging/deltaspike/trunk/content/documentation/bean-validation.html websites/staging/deltaspike/trunk/content/documentation/build.html websites/staging/deltaspike/trunk/content/documentation/configuration.html websites/staging/deltaspike/trunk/content/documentation/container-control.html websites/staging/deltaspike/trunk/content/documentation/core.html websites/staging/deltaspike/trunk/content/documentation/data.html websites/staging/deltaspike/trunk/content/documentation/index.html websites/staging/deltaspike/trunk/content/documentation/jpa.html websites/staging/deltaspike/trunk/content/documentation/jsf.html websites/staging/deltaspike/trunk/content/documentation/partial-bean.html websites/staging/deltaspike/trunk/content/documentation/projectstage.html websites/staging/deltaspike/trunk/content/documentation/scheduler.html websites/staging/deltaspike/trunk/content/documentation/security.html websites/staging/deltaspike/trunk/content/documentation/servlet.html websites/staging/deltaspike/trunk/content/documentation/source.html websites/staging/deltaspike/trunk/content/documentation/spi.html websites/staging/deltaspike/trunk/content/documentation/test-control.html Propchange: websites/staging/deltaspike/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Mon Dec 15 22:31:42 2014 @@ -1 +1 @@ -1645542 +1645776 Added: websites/staging/deltaspike/trunk/content/documentation/addons.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/addons.html (added) +++ websites/staging/deltaspike/trunk/content/documentation/addons.html Mon Dec 15 22:31:42 2014 @@ -0,0 +1,231 @@ + + + + + + + + +Add-ons + + + + + + + + + + + + + + +
+
+
+ + Apache DeltaSpike [] +
+ +
+ + +
+
+
+ +
+
+
+
+

Add-ons

+
+ +
+ +
+ +
+
+
+

Add-ons extend the functionality of DeltaSpike and several have been developed external to the DeltaSpike project. Brief information is given here about each of the add-ons, with details of where they can be obtained from.

+
+
+
+
+

Monitoring

+
+
+

ds-monitoring-addon provides simple monitoring for several common use-cases (exceptions, performance, audits), collecting information about the monitored method-invocations during a request and enabling you to process the entries based on your requirements. For more information about its use and implementation, see os890: [add-on] monitoring lite with deltaspike.

+
+
+

Source code: https://github.com/os890/ds-monitoring-addon

+
+
+
+
+

Spring Bridge

+
+
+

ds-spring-bridge-addon is a two-way cdi-spring bridge that allows spring-beans to be injected into cdi-beans and vice versa provided the concepts, for example qualifiers, are compatible. For more information about its use and implementation, see os890: [add-on] spring-bridge with deltaspike.

+
+
+

Source code: https://github.com/os890/ds-spring-bridge-addon.

+
+
+
+
+

Disruptor

+
+
+

ds-disruptor-addon improves CDI synchronous event-processing performance by creating a disruptor process for every observer method, enabling CDI synchronous events in conjunction with asynchronous observers. This add-on currently works with Apache TomEE and JBoss AS 7. For more information about its use and implementation, see os890: [add-on] fast event processing with disruptor + deltaspike.

+
+
+

Source code: https://github.com/os890/ds-disruptor-addon

+
+
+
+
+ +
+ +
+

Copyright © 2011-2014 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.

+

Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

+
+ +
+ + + + \ No newline at end of file Added: websites/staging/deltaspike/trunk/content/documentation/articles.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/articles.html (added) +++ websites/staging/deltaspike/trunk/content/documentation/articles.html Mon Dec 15 22:31:42 2014 @@ -0,0 +1,257 @@ + + + + + + + + +Articles and Blogs + + + + + + + + + + + + + + +
+
+
+ + Apache DeltaSpike [] +
+ +
+ + +
+
+
+ +
+
+
+
+

Articles and Blogs

+
+ +
+ +
+ +
+
+
+

You can find lots of content related to DeltaSpike with a quick internet search. But here is a list of some useful articles and blogs to get you started.

+
+
+

If you know of useful DeltaSpike articles or blogs that are not listed, let us know.

+
+
+
+
+

Ongoing

+
+
+ +
+
+
+
+

One-offs

+
+
+ +
+
+
+
+ +
+ +
+

Copyright © 2011-2014 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.

+

Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

+
+ +
+ + + + \ No newline at end of file Modified: websites/staging/deltaspike/trunk/content/documentation/bean-validation.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/bean-validation.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/bean-validation.html Mon Dec 15 22:31:42 2014 @@ -134,7 +134,7 @@ body { data-target=".nav-collapse"> Apache DeltaSpike + href="http://deltaspike.apache.org/index.html">Apache DeltaSpike []
    • -
    • Introduction +
    • Overview
      • +
    • Configure Your Projects + +
      • +
    • Use the Module Features
      • Scoping
      • Code Requirements
        • @@ -179,38 +185,72 @@ body {
        -

        Introduction

        +

        Overview

        +
        +
        +

        The Bean Validation module provides CDI integration for bean validation. It enables the creation of CDI-aware ConstraintValidator methods that can use business objects (EJBs, ManagedBeans) to support validation needs.

        +
        +
        +
        +
        +

        Configure Your Projects

        -

        The main feature of the Bean Validation module is to provide CDI -integration in to ConstraintValidator `s. This allows you to inject CDI -objects, EJBs etc in to your validators.

        +

        The configuration information provided here is for Maven-based projects and it assumes that you have already declared the DeltaSpike version and DeltaSpike Core module for your projects, as detailed in Configure DeltaSpike in Your Projects. For Maven-independent projects, see Configure DeltaSpike in Maven-independent Projects.

        -

        Scoping

        +

        Declare Bean Validation Module Dependencies

        -

        ConstraintValidator `s will inherit whatever scope as defined in the bean class.

        +

        Add the Bean Validation module to the list of dependencies in the project pom.xml file using this code snippet:

        +
        +
        +
        +
        <dependency>
+    <groupId>org.apache.deltaspike.modules</groupId>
+    <artifactId>deltaspike-bean-validation-module-impl</artifactId>
+    <version>${deltaspike.version}</version>
+    <scope>runtime</scope>
+</dependency>
        +
        +
        +
        +
        +
        +

        Use the Module Features

        +
        +
        +

        Scoping

        -

        Inherently, a ConstraintValidator may be invoked by multiple threads so please keep that in mind when using them. -You should consider using at least RequestScoped validators.

        +

        A ConstraintValidator inherits the scope defined in the bean class.

        +
        +
        + + + + + +
        +
        Note
        +        		 +A ConstraintValidator may be invoked by multiple threads. For this reason, you should consider using at least RequestScoped validators. +

        Code Requirements

        There are no compile dependencies to use the Bean Validation module. You -simply need to override the factory, either in Java:

        +simply need to override the factory. Then you can build your ConstraintValidator based on CDI programming rules.

        +
        Overriding in Java
        Validation.byDefaultProvider().configure().constraintValidatorFactory(new CDIAwareConstraintValidatorFactory()).buildValidatorFactory()
        -
        -

        Or in XML:

        -
        +
        Overriding in XML
        <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -219,10 +259,6 @@ simply need to override the factory, eit
 </validation-config>
        -
        -

        And then you can simply build your `ConstraintValidator`s based on CDI -programming rules.

        -
        Modified: websites/staging/deltaspike/trunk/content/documentation/build.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/build.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/build.html Mon Dec 15 22:31:42 2014 @@ -6,7 +6,7 @@ -Building DeltaSpike from source +Build and Test DeltaSpike from Source @@ -134,7 +134,7 @@ body { data-target=".nav-collapse"> Apache DeltaSpike + href="http://deltaspike.apache.org/index.html">Apache DeltaSpike []
        • -

          Building DeltaSpike from source

          +

          Build and Test DeltaSpike from Source

          -
          -

          Introduction

          +
          -

          Deltaspike uses maven build tool to automate the compilation, testing and packaging of the project

          -
          -
          -

          Full build

          -
          -
          -
          mvn clean install
          -
          -
          -
          -
          -

          Build with test

          -
          -
          -
          mvn clean install -POWB //execute the unit tests with OpenWebBeans
-or
-mvn clean install -PWeld //execute the unit tests with Weld
          -
          +

          The DeltaSpike source (modules and examples) is provided for inspection, contribution and testing purposes. The source must be built with Maven, which has been used to automate the compilation, testing and packaging processes. Arquillian tests are included with the source and a CDI implementation or container can be specified with which to carry out the tests.

          -
          -
          -

          Integration Tests

          -
          -

          With the unpack Maven-Plugin all Arquillian-Tests get copied to the -integration-test module. Together with the special integration-tests -they get executed via a remote container. Currently we have -configurations for the following containers.

          -
          -
          -

          TomEE

          -
          -

          Executing the Arquillian tests with Apache TomEE

          -
          -
          -
          -
          mvn clean install -Ptomee-build-managed
          -
          -
          -
          -
          -

          JBoss AS7

          -
          -
          Without existing AS7
          -

          Executing the Arquillian tests with JBoss AS7 (without AS7 installation)

          +

          In all cases, to obtain the DeltaSpike source, download deltaspike-project-<version>-source-release.zip and extract the contents.

          -
          -
          -
          mvn clean install -Pjbossas-build-managed-7
          -
          -
          -
          -
          -
          With existing AS7
          -
          -

          Set JBoss_HOME

          -
          -
          -

          Executing the Arquillian tests with JBoss AS7 (AS7 installation -required)

          +
          + + + + + +
          +
          Note
          +          		 +You can also obtain the DeltaSpike source from the project Git repository. The repository is subject to change and it can be used for contributing but should not be used in production environments. For more information, see Contribute to the DeltaSpike Source. +
          -
          -
          -
          mvn clean install -Pjbossas-managed-7
          -
          -
          -
          -

          WildFly 8

          -
          -
          Without existing WF8
          +
          +

          Build without CDI Implementation Tests

          +
          -

          Executing the Arquillian tests with JBoss-WF8 (without WF8 installation)

          +

          DeltaSpike can be built without executing tests against a CDI implementation, with the following commands:

          -
          mvn clean install -Pwildfly-build-managed
          +
          $ cd /path/to/deltaspike-project-<version>/
+$ mvn clean install
          -
          -
          With existing WF8
          -
          -

          Set WILDFLY_HOME

          +
          +

          Build and Test with a CDI Implementation

          +
          -

          Executing the Arquillian tests with JBoss-WF8 (WF8 installation -required)

          -
          -
          -
          -
          mvn clean install -Pwildfly-managed
          +

          Tests can be executed with both the JBoss Weld and Apache OpenWebBeans CDI implementations.

          + + ++++ + + + + + + + + + + + + + + + + +
          Table 1. Build Tests
          ContainerCommand to Execute Arquillian Tests

          JBoss Weld

          +
          +
          $ mvn clean install -PWeld
          +
          +

          Apache OpenWebBeans

          +
          +
          $ mvn clean install -POWB
          +
          +
          -
          -
          -

          GlassFish 3.1

          -
          -
          Without existing GF3
          +
          +

          Build and Test with a CDI Container

          +
          -

          Executing the Arquillian tests with GF3 (without GF3 installation)

          +

          Tests can be executed with JBoss Weld and Apache OpenWebBeans through Java EE 6+ application servers and containers. Configurations are currently provided as details in the table here.

          -
          -
          -
          mvn clean install -Pglassfish-build-managed-3
          -
          -
          -
          -
          -
          With existing GF3
          -
          + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Table 2. Integration Tests
          ContainerCommand to Execute Arquillian Tests

          Apache TomEE

          +
          +
          $ mvn clean install -Ptomee-build-managed
          +
          +

          JBoss AS7 (without AS7 installation)

          +
          +
          $ mvn clean install -Pjbossas-build-managed-7
          +
          +

          JBoss AS7 (AS7 installation required)

          +

          Set JBoss_HOME

          +
          +
          +
          +
          $ mvn clean install -Pjbossas-managed-7
          +
          +

          JBoss WildFly 8 (without WildFly 8 installation)

          +
          +
          mvn clean install -Pwildfly-build-managed
          +
          +

          JBoss WildFly 8 (WildFly 8 installation required)

          +

          Set WILDFLY_HOME

          +
          +
          +
          +
          $ mvn clean install -Pwildfly-managed
          +
          +

          Oracle GlassFish 3 (without GlassFish 3 installation)

          +
          +
          mvn clean install -Pglassfish-build-managed-3
          +
          +

          Oracle GlassFish 3.1 (GlassFish 3.1 installation required)

          Install GlassFish (default setup without admin-password) and start -GlassFish with asadmin start-domain and asadmin start-database

          -
          -
          -

          Executing the Arquillian tests with Oracle Glassfish 3.1+

          +GlassFish with asadmin start-domain and asadmin start-database.

          -
          mvn clean install -Pglassfish-remote-3.1
          -
          -
          +
          $ mvn clean install -Pglassfish-remote-3.1
          - -
          -

          GlassFish 4

          -
          -
          Without existing GF4
          -
          -

          Executing the Arquillian tests with GF4 (without GF4 installation)

          -
          -
          +

          Oracle GlassFish 4 (without Oracle GlassFish 4 installation)

          -
          mvn clean install -Pglassfish-build-managed-4
          -
          +
          mvn clean install -Pglassfish-build-managed-4
          -
          - -
          -

          WebLogic 12c

          -
          -

          Install WebLogic 12c. Start Confiuration Wizard to create a new basic +

          Oracle WebLogic 12c

          +

          Install WebLogic 12c. Start Configuration Wizard to create a new basic WebLogic Domain. Default options and domain name = base_domain, administrator user name = weblogic1, administrator password = weblogic1. -Set WLS_HOME so that %WLS_HOME%.jar exists. Start the domain.

          -
          -
          -

          Executing the Arquillian tests with Oracle WebLogic 12c

          +Set WLS_HOME so that %WLS_HOME%.jar exists. Start the domain.

          -
          mvn clean install -Pwls-remote-12c
          +
          $ mvn clean install -Pwls-remote-12c
          +
          -
          -
          -

          Jenkins Builds

          -
          -

          https://builds.apache.org/view/A-D/view/DeltaSpike/

          -
          -
          -
          -

          Sonar

          -
          -

          https://analysis.apache.org/dashboard/index/org.apache.deltaspike:deltaspike-project

          -
          +
          +

          Next

          +
          +
          +
          Added: websites/staging/deltaspike/trunk/content/documentation/cdiimp.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/cdiimp.html (added) +++ websites/staging/deltaspike/trunk/content/documentation/cdiimp.html Mon Dec 15 22:31:42 2014 @@ -0,0 +1,461 @@ + + + + + + + + +Enable CDI For Your Java Environment + + + + + + + + + + + + + + +
          +
          +
          + + Apache DeltaSpike [] +
          + +
          + + +
          +
          +
          + +
          +
          +
          +
          +

          Enable CDI For Your Java Environment

          +
          + +
          + +
          + +
          +
          +
          +

          DeltaSpike requires a CDI implementation to be available in the Java environment where your projects are deployed. The implementation provides the CDI essentials, managing dependency injection and contextual lifecycles. JBoss Weld and Apache OpenWebBeans (OWB) are two widely used CDI implementations. Dependent on the Java environment you choose, some setup may be necessary as detailed here.

          +
          +
          +
          +
          +

          Java EE6+ Containers

          +
          +
          +

          CDI is part of Java EE6 and later so CDI implementations are included as standard in Java EE6+ compliant environments. There is no additional CDI configuration needed besides including the CDI-obligatory beans.xml file in your project.

          +
          +
          +

          JBoss Weld is integrated in Java EE application servers including WildFly, JBoss Enterprise Application Platform, GlassFish, and Oracle WebLogic.

          +
          +
          +

          Apache OpenWebBeans (OWB) is integrated in Java EE containers including Apache TomEE, Apache Geronimo, IBM WebSphere Application Server, and SiwPas.

          +
          +
          +
          +
          +

          Java EE5 and Servlet Containers

          +
          +
          +

          CDI implementations are not distributed with Java EE5 application servers or Servlet-only environments such as Apache TomCat and Eclipse Jetty. You can use CDI in these environments by embedding a standalone CDI implementation. Both JBoss Weld and Apache OpenWebBeans can be used for this task; for more information, see the corresponding CDI implementation documentation.

          +
          +
          +
          +
          +

          Java SE6+

          +
          +
          +

          CDI is not part of Java SE but it can still be used. JBoss Weld and Apache OpenWebBeans implementations can be used to act as dependency injection bean managers but the respective containers must be booted manually.

          +
          +
          +

          DeltaSpike provides a dedicated Container Control module to enable applications deployed in Java SE environments to boot a CDI container. The Container Control module consists of the API component and components specific to the JBoss Weld, Apache OpenWebBeans and Apache OpenEJB CDI containers. The DeltaSpike module provides a layer of abstraction from the specific CDI containers, enabling you to write container-independent code in your project.

          +
          +
          +

          Instructions are provided here for adding the required resources to both Maven-based and Maven-independent projects and subsequently booting the CDI container from your project source code.

          +
          +
          +

          1. Declare CDI Dependencies

          +
          +

          Option A: Declare Dependencies for Maven-based Projects

          +
          +

          For Maven-based projects, the Container Control module is available in Maven Central together with the other DeltaSpike modules. You must configure your project to use the DeltaSpike Container Control API and one of the CDI container-specific modules.

          +
          +
          +
            +
          1. +

            Open the project pom.xml file for editing

            +
            2. +
          2. +

            Add the DeltaSpike Container Control API to the list of dependencies

            +
            +
            +
            <dependency>
+    <groupId>org.apache.deltaspike.cdictrl</groupId>
+    <artifactId>deltaspike-cdictrl-api</artifactId>
+    <version>${deltaspike.version}</version>
+    <scope>compile</scope>
+</dependency>
            +
            +
            +
            3. +
          3. +

            Add CDI container dependencies for one of the container options listed here

            +
            +
            For JBoss Weld
            +
              +
            1. +

              Add the JBoss Weld version to the list of properties, replacing the version as desired

              +
              +
              +
              <properties>
+    <weld.version>1.1.9.Final</weld.version>
+</properties>
              +
              +
              +
              2. +
            2. +

              Add the JBoss Weld dependency to the list of dependencies

              +
              +
              +
              <dependency>
+    <groupId>org.jboss.weld.se</groupId>
+    <artifactId>weld-se</artifactId>
+    <version>${weld.version}</version>
+    <scope>runtime</scope>
+</dependency>
              +
              +
              +
              3. +
            3. +

              Add the DeltaSpike Weld-specific Container Control module to the list of dependencies

              +
              +
              +
              <dependency>
+    <groupId>org.apache.deltaspike.cdictrl</groupId>
+    <artifactId>deltaspike-cdictrl-weld</artifactId>
+    <version>${deltaspike.version}</version>
+    <scope>runtime</scope>
+</dependency>
              +
              +
              +
              4. +
            +
            +
            +
            For Apache OpenWebBeans
            +
              +
            1. +

              Add the Apache OpenWebBeans version to the list of properties, replacing the version as desired

              +
              +
              +
              <properties>
+    <owb.version>1.2.0</owb.version>
+</properties>
              +
              +
              +
              2. +
            2. +

              Add the Apache OpenWebBeans dependencies to the list of dependencies

              +
              +
              +
              <dependency>
+    <groupId>org.apache.openwebbeans</groupId>
+    <artifactId>openwebbeans-impl</artifactId>
+    <version>${owb.version}</version>
+    <scope>runtime</scope>
+</dependency>
+
+<dependency>
+    <groupId>org.apache.openwebbeans</groupId>
+    <artifactId>openwebbeans-spi</artifactId>
+    <version>${owb.version}</version>
+    <scope>compile</scope>
+</dependency>
              +
              +
              +
              3. +
            3. +

              Add the DeltaSpike Apache OpenWebBeans-specific Container Control module to the list of dependencies

              +
              +
              +
              <dependency>
+    <groupId>org.apache.deltaspike.cdictrl</groupId>
+    <artifactId>deltaspike-cdictrl-owb</artifactId>
+    <version>${deltaspike.version}</version>
+    <scope>runtime</scope>
+</dependency>
              +
              +
              +
              4. +
            +
            +
            4. +
          4. +

            Save the pom.xml file changes

            +
            5. +
          5. +

            Download all required dependencies

            +
            +
            +
            mvn clean install
            +
            +
            +
            6. +
          +
          +
          +
          +

          Option B: Declare Dependencies for Maven-independent Projects

          +
          +

          For Maven-independent projects, the Container Control module is distributed together with the other DeltaSpike modules in distribution-fill-<version>.zip. You must add two of the files from the cdictrl directory to your project, namely deltaspike-cdictrl-api.jar and the .jar file that corresponds to the CDI container you have chosen. Add these files to the project WEB-INF/lib or EAR/lib directory for .war and .ear projects respectively.

          +
          +
          +
          +
          +

          2. Start the CDI Container from Your Project

          +
          +

          To start a CDI container in your application, you must instantiate a CdiContainer object and call the #boot method. When #boot is called, the CdiContainer scans CDI-enabled +archives for beans and CDI extensions. Before the application exits, #shutdown must be called to correctly destroy all beans. An example is given in the code snippet here.

          +
          +
          +
          +
          import org.apache.deltaspike.cdise.api.CdiContainer;
+import org.apache.deltaspike.cdise.api.CdiContainerLoader;
+
+public class MainApp {
+    public static void main(String[] args) {
+
+        CdiContainer cdiContainer = CdiContainerLoader.getCdiContainer();
+        cdiContainer.boot();
+
+        // You can use CDI here
+
+        cdiContainer.shutdown();
+    }
+}
          +
          +
          +
          +

          Starting the container does not automatically start all CDI Contexts. Contexts must be started independently using the provided ContextControl class. An example of starting the Context for @ApplicationScoped beans is added to the code snippet here.

          +
          +
          +
          +
          import org.apache.deltaspike.cdise.api.CdiContainer;
+import org.apache.deltaspike.cdise.api.CdiContainerLoader;
+import org.apache.deltaspike.cdise.api.ContextControl;
+import javax.enterprise.context.ApplicationScoped;
+
+public class MainApp {
+    public static void main(String[] args) {
+
+        CdiContainer cdiContainer = CdiContainerLoader.getCdiContainer();
+        cdiContainer.boot();
+
+        // Starting the application-context enables use of @ApplicationScoped beans
+        ContextControl contextControl = cdiContainer.getContextControl();
+        contextControl.startContext(ApplicationScoped.class);
+
+        // You can use CDI here
+
+        cdiContainer.shutdown();
+    }
+}
          +
          +
          +
          +

          To resolve project beans, you can use the DeltaSpike BeanProvider class. Whether EchoService is a concrete implementation or just an interface depends on the application. In the case that it is an interface, the corresponding implementation is resolved. The resolved bean is a standard CDI bean and it can be used for all CDI concepts, such as @Inject, in the class without further uses of BeanProvider. An example of resolving the bean without qualifiers is given in the code snippet here.

          +
          +
          +
          +
          EchoService echoService = BeanProvider.getContextualReference(EchoService.class, false);
          +
          +
          +
          +
          +
          +
          +

          Next

          +
          +
          + +
          +
          +
          +
          + +
          + +
          +

          Copyright © 2011-2014 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.

          +

          Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

          +
          + +
          + + + + \ No newline at end of file Modified: websites/staging/deltaspike/trunk/content/documentation/configuration.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/configuration.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/configuration.html Mon Dec 15 22:31:42 2014 @@ -134,7 +134,7 @@ body { data-target=".nav-collapse"> Apache DeltaSpike + href="http://deltaspike.apache.org/index.html">Apache DeltaSpike []
        • ConfigSource
          • -
        • Type-safe configuration
          • +
        • Type-safe Configuration
        @@ -233,7 +233,7 @@ settings, JNDI or the current Drop-In Configuration

        This mechanism also allows for dynamic configuration in case of a JAR -drop-in. By adding some JAR to the classpath, all it’s contained +drop-in. By adding some JAR to the classpath, all its contained configuration will get picked up and considered in the property value evaluation. You could also use this mechanism to switch implementations of some SPI (Service Provider Interface) in your own code.

        @@ -242,17 +242,17 @@ of some SPI (Service Provider Interface)

        CDI-Extension Configuration

        -

        In some cases low-level configs are needed e.g. during the bootstrapping +

        In some cases low-level configs are needed, for example during the bootstrapping process of the CDI container.

        The good news: our DeltaSpike configuration mechanism does not rely on any other EE mechanism to be booted. Which means it can perfectly get -used to even configure those parts itself. Since the mechanism doesn’t +used to even configure those parts itself. Since the mechanism does not rely on CDI it can for example be used to configure CDI-Extensions.

        -

        Currently this is e.g. used to configure the value of the current ProjectStage, configured values which can be +

        Currently this is, for example, used to configure the value of the current ProjectStage, configured values which can be used in the expressions for @Exclude, 'Deactivatable', etc. DeltaSpike needs such a low-level approach for several features internally, but users can utilize it for their own needs as well. This is done by using @@ -376,23 +376,30 @@ the following lookup chain is used until

        -

        handling of default values

        +

        Handling of Default Values

        There is a 2nd variant of all those methods where it is possible to provide a default value which gets returned instead of null or if the final result is an empty String.

        -
        -

        Performance Hint:

        -
        -
        -

        The only ConfigResolver operation which is cached is the determination +

        + + + + + +
        +
        Tip
        +        		 +
        Performance Hint
        +The only ConfigResolver operation which is cached is the determination of the ConfigSources. The various getPropertyValue operations are not cached in the ConfigResolver but might be cached in the ConfigSources. This makes the overall calculation a bit slower, but allows for values -to change dynamically if someone likes to e.g. implement a +to change dynamically if someone likes to for example implement a JmxConfigSource (not yet part of DeltaSpike, but easily -implementable).

        +implementable). +
        @@ -401,7 +408,7 @@ implementable).

        ConfigSource

        -

        A ConfigSource is exactly what it’s name says: a source for configured +

        A ConfigSource is exactly what its name says: a source for configured values. The ConfigResolver uses all configured implementations of ConfigSource to lookup the property in question.

        @@ -416,9 +423,9 @@ ConfigSources have a higher deltas pickup the values from within the release binaries.

        -

        ConfigSources provided by default

        +

        ConfigSources Provided by Default

        -

        Per default there are implementations for the following config sources +

        By default there are implementations for the following configuration sources (listed in the lookup order):

        @@ -438,49 +445,64 @@ pickup the values from within the releas
-

It’s possible to change this order and to add custom config sources.

+

It is possible to change this order and to add custom configuration sources.

-
-

Note: Important Hints esp. for custom implementations: - The -config-source with the highest ordinal gets used first. - If a custom +

+ + + + + +
+
Tip
+		 +
Important Tips Especially for Custom Implementations
+- The config-source with the highest ordinal gets used first. - If a custom implementation should be invoked before the default implementations, -use an ordinal-value > 400 - If a custom implementation should be -invoked after the default implementations, use an ordinal-value < 100 +use an ordinal-value > 400. - If a custom implementation should be +invoked after the default implementations, use an ordinal-value < 100. - The ConfigResolver performs no caching. If your custom ConfigSource operation is expensive, then you might think about introducing some -caching.

+caching. +
-

Reordering of the default order of Config-Sources

+

Reordering of the Default Order of ConfigSources

To change the lookup order, you have to configure the ordinal in the -corresponding config source (e.g. to change the config ordinal of the -config source for system properties, you have to set the system property +corresponding configuration source (e.g. to change the configuration ordinal of the +configuration source for system properties, you have to set the system property with the ordinal key 'deltaspike_ordinal' and the new value).

Example with /META-INF/apache-deltaspike.properties: If the properties file/s should be used before the other implementations, you have to -configure an ordinal > 400. That means, you have to add e.g. +configure an ordinal > 400. That means, you have to add for example deltaspike_ordinal=401.

Each single property file is treated as own ConfigSource and thus can have different deltaspike_ordinal values!

-
-

Hint:

-
-
-

In case of property files which are supported by default +

+ + + + + +
+
Note
+		 +In case of property files which are supported by default (/META-INF/apache-deltaspike.properties) every file is handled as independent config-source, but all of them have ordinal 400 by default -(and can be reordered in a fine-grained manner).

+(and can be reordered in a fine-grained manner). +
-

Custom Config-Sources

+

Custom ConfigSources

ConfigSources are picked up using the `java.util.ServiceLoader' mechanism.

@@ -495,7 +517,7 @@ into it.

If you need dynamic ConfigSources you can also register a ConfigSourceProvider in a similar way. This is useful if you like to -dynamically pick up multiple ConfigSources of the same kind. E.g. if you +dynamically pick up multiple ConfigSources of the same kind. For example, if you like to pick up all myproject.properties files from all the JARs in your classpath.

@@ -503,14 +525,20 @@ your classpath.

Please note that a single ConfigSource should be either registered directly or via a ConfigSourceProvider, but never both ways.

-
-

Important Hint:

-
-
-

Have a look at the abstract base-implementation of ConfigSource +

+ + + + + +
+
Tip
+		 +Have a look at the abstract base-implementation of ConfigSource DeltaSpike is using internally, if a custom implementation should load the ordinal value from the config-source like the default -implementations provided by DeltaSpike do.

+implementations provided by DeltaSpike do. +

PropertyFileConfig

@@ -554,7 +582,7 @@ dependency to the module that contains t
-

Type-safe configuration

+

Type-safe Configuration

DeltaSpike provides a way to directly inject configured values into your