Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 51863200B74 for ; Thu, 18 Aug 2016 02:38:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5011D160ABE; Thu, 18 Aug 2016 00:38:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 29EA7160A8C for ; Thu, 18 Aug 2016 02:38:17 +0200 (CEST) Received: (qmail 3502 invoked by uid 500); 18 Aug 2016 00:38:16 -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 3493 invoked by uid 99); 18 Aug 2016 00:38:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2016 00:38:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D0F81C0BCA for ; Thu, 18 Aug 2016 00:38:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.374 X-Spam-Level: X-Spam-Status: No, score=0.374 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 1WcoeBf4Rhkh for ; Thu, 18 Aug 2016 00:38:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 937585FB37 for ; Thu, 18 Aug 2016 00:38:03 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DA17AE0220 for ; Thu, 18 Aug 2016 00:38:02 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id CC9783A0184 for ; Thu, 18 Aug 2016 00:38:02 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r995350 [1/18] - in /websites/staging/deltaspike/trunk/content: ./ documentation/ Date: Thu, 18 Aug 2016 00:38:02 -0000 To: commits@deltaspike.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160818003802.CC9783A0184@svn01-us-west.apache.org> archived-at: Thu, 18 Aug 2016 00:38:19 -0000 Author: buildbot Date: Thu Aug 18 00:38:02 2016 New Revision: 995350 Log: Staging update by buildbot for deltaspike 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/cdiimp.html websites/staging/deltaspike/trunk/content/documentation/configuration.html websites/staging/deltaspike/trunk/content/documentation/configure.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/modules.html websites/staging/deltaspike/trunk/content/documentation/overview.html websites/staging/deltaspike/trunk/content/documentation/partial-bean.html websites/staging/deltaspike/trunk/content/documentation/projectstage.html websites/staging/deltaspike/trunk/content/documentation/proxy.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/snapshots.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 Thu Aug 18 00:38:02 2016 @@ -1 +1 @@ -1756697 +1756698 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 Thu Aug 18 00:38:02 2016 @@ -1,410 +1,410 @@ - - - - - - - - - - - - - Bean Validation Module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
-
-

Bean Validation Module

-
- -
-
-

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.

-
-
-
-
-

Project Setup

-
-
-

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.

-
-
-

Declare Bean Validation Module Dependencies

-
-

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

Or if you’re using Gradle, add these dependencies to your build.gradle:

-
-
-
-
     runtime 'org.apache.deltaspike.modules:deltaspike-bean-validation-module-impl'
-
-
-
-
-
-
-

Scoping

-
-
-

A ConstraintValidator inherits the scope defined in the bean class.

-
-
- - - - - -
- - -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. Then you can build your ConstraintValidator based on CDI programming rules.

-
-
-
Overriding in Java
-
-
Validation.byDefaultProvider().configure().constraintValidatorFactory(new CDIAwareConstraintValidatorFactory()).buildValidatorFactory()
-
-
-
-
Overriding in XML
-
-
<validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration">
-    <constraint-validator-factory>org.apache.deltaspike.beanvalidation.impl.CDIAwareConstraintValidatorFactory</constraint-validator-factory>
-</validation-config>
-
-
-
-
-
-
- - -
-
-
- -
-
- - - -
- - -
-
-
-
-

Copyright © 2011-2016 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.

-
-
-
- - + + + + + + + + + + + + + Bean Validation Module + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + + +
+
+

Bean Validation Module

+
+ +
+
+

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.

+
+
+
+
+

Project Setup

+
+
+

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.

+
+
+

Declare Bean Validation Module Dependencies

+
+

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

Or if you’re using Gradle, add these dependencies to your build.gradle:

+
+
+
+
     runtime 'org.apache.deltaspike.modules:deltaspike-bean-validation-module-impl'
+
+
+
+
+
+
+

Scoping

+
+
+

A ConstraintValidator inherits the scope defined in the bean class.

+
+
+ + + + + +
+ + +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. Then you can build your ConstraintValidator based on CDI programming rules.

+
+
+
Overriding in Java
+
+
Validation.byDefaultProvider().configure().constraintValidatorFactory(new CDIAwareConstraintValidatorFactory()).buildValidatorFactory()
+
+
+
+
Overriding in XML
+
+
<validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration">
+    <constraint-validator-factory>org.apache.deltaspike.beanvalidation.impl.CDIAwareConstraintValidatorFactory</constraint-validator-factory>
+</validation-config>
+
+
+
+
+
+
+ + +
+
+
+ +
+
+ + + +
+ + +
+
+
+
+

Copyright © 2011-2016 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/build.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation/build.html (original) +++ websites/staging/deltaspike/trunk/content/documentation/build.html Thu Aug 18 00:38:02 2016 @@ -1,566 +1,566 @@ - - - - - - - - - - - - - Build and Test DeltaSpike from Source - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
-
-

Build and Test DeltaSpike from Source

-
- -
-
-
-
-

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.

-
-
-

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

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

Build without CDI Implementation Tests

-
-
-

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

-
-
-
-
$ cd /path/to/deltaspike-project-1.7.1/
-$ mvn clean install
-
-
-
-
-
-

Build and Test with a CDI Implementation

-
-
-

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 1.x (CDI 1.0)

-
-
$ mvn clean install -PWeld1 -Dweld.version=1.1.33.Final
-
-

JBoss Weld 2.x (CDI 1.2)

-
-
$ mvn clean install -PWeld2 -Dweld.version=2.3.4.Final
-
-

JBoss Weld 3.x (CDI 2.0)

-
-
$ mvn clean install -PWeld3 -Dweld.version=3.0.0.Alpha16
-
-

Apache OpenWebBeans

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

Build and Test with a CDI Container

-
-
-

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.

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

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

Oracle GlassFish 4 (without Oracle GlassFish 4 installation)

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

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.

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

Build and Debug with a Java EE6+ application servers

-
-
-

Tests can be debugged through Java EE 6+ application servers. Configurations are currently provided as details in the table here.

-
- - ---- - - - - - - - - - - - - -
Table 3. Integration Tests with debug
ContainerCommand to Execute Arquillian Tests with remote debugging

Apache TomEE

-

Use remote debuggig at port 5005

-
-
-
-
mvn test -Ptomee-build-managed -Dtest=UnitTestName -Dopenejb.server.debug=true
-
-
-
-
-
-

Next

-
-
- -
-
-
-
-
- - - - - -
-
-
-
-

Copyright © 2011-2016 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.

-
-
-
- - + + + + + + + + + + + + + Build and Test DeltaSpike from Source + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + + +
+
+

Build and Test DeltaSpike from Source

+
+ +
+
+
+
+

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.

+
+
+

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

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

Build without CDI Implementation Tests

+
+
+

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

+
+
+
+
$ cd /path/to/deltaspike-project-1.7.1/
+$ mvn clean install
+
+
+
+
+
+

Build and Test with a CDI Implementation

+
+
+

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 1.x (CDI 1.0)

+
+
$ mvn clean install -PWeld1 -Dweld.version=1.1.33.Final
+
+

JBoss Weld 2.x (CDI 1.2)

+
+
$ mvn clean install -PWeld2 -Dweld.version=2.3.4.Final
+
+

JBoss Weld 3.x (CDI 2.0)

+
+
$ mvn clean install -PWeld3 -Dweld.version=3.0.0.Alpha16
+
+

Apache OpenWebBeans

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

Build and Test with a CDI Container

+
+
+

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.

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

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

Oracle GlassFish 4 (without Oracle GlassFish 4 installation)

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

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.

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

Build and Debug with a Java EE6+ application servers

+
+
+

Tests can be debugged through Java EE 6+ application servers. Configurations are currently provided as details in the table here.

+
+ + ++++ + + + + + + + + + + + + +
Table 3. Integration Tests with debug
ContainerCommand to Execute Arquillian Tests with remote debugging

Apache TomEE

+

Use remote debuggig at port 5005

+
+
+
+
mvn test -Ptomee-build-managed -Dtest=UnitTestName -Dopenejb.server.debug=true
+
+
+
+
+
+

Next

+
+
+ +
+
+
+
+
+ + + + + +
+
+
+ +
+
+ + \ No newline at end of file