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 63D63200B74 for ; Thu, 18 Aug 2016 02:37:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 624B0160AC0; Thu, 18 Aug 2016 00:37:20 +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 345C6160A8C for ; Thu, 18 Aug 2016 02:37:18 +0200 (CEST) Received: (qmail 412 invoked by uid 500); 18 Aug 2016 00:37:17 -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 403 invoked by uid 99); 18 Aug 2016 00:37:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2016 00:37:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D81D51804CC for ; Thu, 18 Aug 2016 00:37:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id gxGi7jZMsbOK for ; Thu, 18 Aug 2016 00:37:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 0C2425F64D for ; Thu, 18 Aug 2016 00:37:01 +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 24236E58E2 for ; Thu, 18 Aug 2016 00:36:57 +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 095343A2B77 for ; Thu, 18 Aug 2016 00:36:57 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r1756698 [11/18] - /deltaspike/site/trunk/content/documentation/ Date: Thu, 18 Aug 2016 00:36:56 -0000 To: commits@deltaspike.apache.org From: johndament@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160818003657.095343A2B77@svn01-us-west.apache.org> archived-at: Thu, 18 Aug 2016 00:37:20 -0000 Modified: deltaspike/site/trunk/content/documentation/modules.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/modules.html?rev=1756698&r1=1756697&r2=1756698&view=diff ============================================================================== --- deltaspike/site/trunk/content/documentation/modules.html (original) +++ deltaspike/site/trunk/content/documentation/modules.html Thu Aug 18 00:36:56 2016 @@ -1,350 +1,350 @@ - - - - - - - - - - - - - Overview of DeltaSpike Modules - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
-
-

Overview of DeltaSpike Modules

-
- -
-
-

DeltaSpike consists of ready-to-use modules. These include a core module and a number of optional modules for providing additional enterprise functionality to your applications. An overview of each module is provided here and for more information see the linked individual module pages.

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

Core

-

For fundamental and defining DeltaSpike API and utility classes

-

Bean Validation

-

For adding CDI support in Bean Validation, enabling creation of CDI aware ConstraintValidator methods that can use business objects (EJBs, ManagedBeans) to support validation needs

-

Container Control

-

For CDI container booting and shutdown and associated context lifecycle management

-

Data

-

For an enhanced JPA experience with declarative queries, reducing boilerplate to a minimum

-

JPA

-

For transactional context and scope

-

JSF

-

For CDI integration with JSF, with type-safe view config, multi-window handling, new scopes (WindowScoped, ViewScope, ViewAccessScoped, GroupedConversationScoped) and integration with DeltaSpike “core” messages and exception handling

-

Partial-Bean

-

For implementing a generic handler to replace manual implementations of interfaces (or abstract classes)

-

Scheduler

-

For simple integration with Quartz v2 (default) or any other scheduler that supports cron-expressions for job-classes

-

Security

-

For intercept and security checking on method calls

-

Servlet

-

For integration with the Java Servlet API, enabling injection of common servlet objects and propagation of servlet events to the CDI event bus

-

Test-Control

-

For writing CDI-based tests easily

-
-
-
- - - -
-
-
-
-

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.

-
-
-
- - + + + + + + + + + + + + + Overview of DeltaSpike Modules + + + + + + + + + + + + + + + + + + + + + +
+
+ + + +
+
+

Overview of DeltaSpike Modules

+
+ +
+
+

DeltaSpike consists of ready-to-use modules. These include a core module and a number of optional modules for providing additional enterprise functionality to your applications. An overview of each module is provided here and for more information see the linked individual module pages.

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

Core

+

For fundamental and defining DeltaSpike API and utility classes

+

Bean Validation

+

For adding CDI support in Bean Validation, enabling creation of CDI aware ConstraintValidator methods that can use business objects (EJBs, ManagedBeans) to support validation needs

+

Container Control

+

For CDI container booting and shutdown and associated context lifecycle management

+

Data

+

For an enhanced JPA experience with declarative queries, reducing boilerplate to a minimum

+

JPA

+

For transactional context and scope

+

JSF

+

For CDI integration with JSF, with type-safe view config, multi-window handling, new scopes (WindowScoped, ViewScope, ViewAccessScoped, GroupedConversationScoped) and integration with DeltaSpike “core” messages and exception handling

+

Partial-Bean

+

For implementing a generic handler to replace manual implementations of interfaces (or abstract classes)

+

Scheduler

+

For simple integration with Quartz v2 (default) or any other scheduler that supports cron-expressions for job-classes

+

Security

+

For intercept and security checking on method calls

+

Servlet

+

For integration with the Java Servlet API, enabling injection of common servlet objects and propagation of servlet events to the CDI event bus

+

Test-Control

+

For writing CDI-based tests easily

+
+
+
+ + + +
+
+
+
+

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: deltaspike/site/trunk/content/documentation/overview.html URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/documentation/overview.html?rev=1756698&r1=1756697&r2=1756698&view=diff ============================================================================== --- deltaspike/site/trunk/content/documentation/overview.html (original) +++ deltaspike/site/trunk/content/documentation/overview.html Thu Aug 18 00:36:56 2016 @@ -1,503 +1,503 @@ - - - - - - - - - - - - - Overview of DeltaSpike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- - - -
-
-

Overview of DeltaSpike

-
- -
-
-
-
-

Apache DeltaSpike is a collection of portable CDI extensions. These ready-to-use modules enable you to integrate tested API extensions into your Java projects.

-
-
-

DeltaSpike consists of a core module and a number of optional modules for providing additional -enterprise functionality to your applications. The modules include features for enhanced security with type-safe -control over method invocations, integration with schedulers, injection of CDI objects into validators, a -transactional context and scope, and much more. DeltaSpike also provides boot and shutdown control over CDI containers -in Java SE applications.

-
-
-

As a CDI extension, DeltaSpike must be used in conjunction with a CDI implementation and supports both JBoss Weld -and Apache OpenWebBeans. DeltaSpike is tested on a range of application servers and CDI-enabled containers -including Apache TomEE, JBoss AS, WildFly, Oracle GlassFish, and Jetty.

-
-
-

DeltaSpike provides a number of examples to show you how to use and get -the most from this technology.

-
-
-
-
-

Features

-
-
-

Java EE 7 without Java EE 7!

-
-

Transactional support for non-EJB beans: The Transactional Interceptor in DeltaSpike paved the way for -@Transactional in Java EE 7.

-
-
-

Injectable Servlet objects: Enables CDI injection in Servlets in Java EE 6/CDI 1.0 environments

-
-
-

Injectable resources: Configuration, resource bundles,…​ are easy to inject when using CDI and Apache DeltaSpike.

-
-
-

@Exclude annotation: Lets you prevent classes from being treated as CDI beans even if they are in a CDI-enabled -archive in a Java EE 6/CDI 1.0 environment where @Vetoed is unavailable or when you need to veto based on -ProjectStages or expressions.

-
-
-

Scheduling tasks: Async processes in a non-EE7 environment.

-
-
-

Bean Validation integration: Injection of CDI beans and EJBs into Constraint Validators.

-
-
-

BeanProvider: Access the BeanManager and CDI beans even in non-managed classes like JPA 2.0 EntityListeners or -Spring Beans.

-
-
-
-

JSF Improvements

-
-

Multi-window handling: Management of logical windows for batch jobs, browser tab separation in JSF and more.

-
-
-

Type-safe view-config: Lets you bind metadata (e.g. for security) to views with a flexible type-safe approach. It -provides a more solid navigation in case of JSF and helps a lot in the maintenance phase.

-
-
-

View-Controller: Based on type-safe view-configs, view-controller annotations provide a type-safe alternative to -standard tags.

-
-
-

Injection in Converters and Validators: Inject CDI beans and EJBs into JSF Converters and Validators.

-
-
-

JSF event broadcasting to CDI: Allows CDI to be notified about JSF events

-
-
-
-

Productivity Improvements

-
-

Security based on annotations: The foundation for building a robust, capable and non-invasive security solution.

-
-
-

New CDI scopes: TransactionScoped, WindowScoped, ViewScoped, ViewAccess scope, Grouped conversation scope.

-
-
-

Container Control and Test Control: Java SE with CDI, all with a unifying API. Start, stop, add classes to a running CDI container.

-
-
-

Data Module: An out of the box entity framework solution complete with support for container or application managed persistence contexts, as well as JDBC.

-
-
-

Decoupled Exception handling: Event-based exception handling framework, similar to the CDI event observer mechanism.

-
-
-

JMX integration: Any CDI bean can be exposed via JMX easily with a single annotation.

-
-
-

Type-safe i18n messages: Localized messages are easy to use with an interface and a resource bundle, no more boilerplate and your messages now have context within the code.

-
-
-

Type-safe ProjectStages: Compared to ProjectStages in JSF, DeltaSpike provides a type-safe, but still extensible -approach which can be used in CDI-based applications.

-
-
-
-
-
-

Background

-
-
-

CDI

-
-

Java Contexts and Dependency Injection for the Java EE platform (JSR 299), - abbreviated CDI was introduced as part of Java EE 6. The core features of CDI are as follows:

-
-
-
    -
  • -

    improved stateful object lifecycles with an additional context named Conversation that encompasses a series of requests within one session and lifecycle management by the container according to well-defined contexts

    -
  • -
  • -

    dependency injection conducted in a type-safe manner, with type checking conducted at compilation time so errors are exposed earlier and debugging is easier

    -
  • -
  • -

    event notification facility for object interaction

    -
  • -
  • -

    a better approach for interceptors with annotations binding interceptors to objects and with a new interceptor -named decorator that knows about individual bean attributes through inheritance and is more appropriate for use in - solving business problems

    -
  • -
  • -

    a Service Provider Interface (SPI) for developing portable extensions to the CDI container

    -
  • -
-
-
-

CDI is a Java Community Process (JCP) standard. All Java EE 6 compliant -application servers must provide support for CDI. JBoss Weld is a reference -implementation of the CDI specification and other spec-compliant implementations exist such as Apache OpenWebBeans (OWB). While CDI is a Java EE 6 essential, CDI can also be used in Java SE environments with the aid of standalone CDI implementations.

-
-
-
-

Portable CDI Extensions

-
-

The CDI Service Provider Interface (SPI) is exposed to enable extension of the CDI feature set by third parties. -Portable CDI extensions extend CDI implementations and improve existing Java EE APIs by enabling integration of different technologies.

-
-
-

As set out in the CDI specification, a portable CDI extension may integrate with a CDI container as follows:

-
-
-
    -
  • -

    providing its own beans, interceptors and decorators to the container

    -
  • -
  • -

    injecting dependencies into its own objects using the dependency injection service

    -
  • -
  • -

    providing a context implementation for a custom scope

    -
  • -
  • -

    augmenting or overriding the annotation-based metadata with metadata from some other source

    -
  • -
-
-
-

As indicated by the name, portable CDI extensions can be used with any spec-compliant CDI implementation.

-
-
-
-
-
-

Next

-
-
-

For instructions on how to start using DeltaSpike, see Configure DeltaSpike in Your Projects and Enable CDI For Your Java Environment.

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

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.

-
-
-
- - + + + + + + + + + + + + + Overview of DeltaSpike + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + + +
+
+

Overview of DeltaSpike

+
+ +
+
+
+
+

Apache DeltaSpike is a collection of portable CDI extensions. These ready-to-use modules enable you to integrate tested API extensions into your Java projects.

+
+
+

DeltaSpike consists of a core module and a number of optional modules for providing additional +enterprise functionality to your applications. The modules include features for enhanced security with type-safe +control over method invocations, integration with schedulers, injection of CDI objects into validators, a +transactional context and scope, and much more. DeltaSpike also provides boot and shutdown control over CDI containers +in Java SE applications.

+
+
+

As a CDI extension, DeltaSpike must be used in conjunction with a CDI implementation and supports both JBoss Weld +and Apache OpenWebBeans. DeltaSpike is tested on a range of application servers and CDI-enabled containers +including Apache TomEE, JBoss AS, WildFly, Oracle GlassFish, and Jetty.

+
+
+

DeltaSpike provides a number of examples to show you how to use and get +the most from this technology.

+
+
+
+
+

Features

+
+
+

Java EE 7 without Java EE 7!

+
+

Transactional support for non-EJB beans: The Transactional Interceptor in DeltaSpike paved the way for +@Transactional in Java EE 7.

+
+
+

Injectable Servlet objects: Enables CDI injection in Servlets in Java EE 6/CDI 1.0 environments

+
+
+

Injectable resources: Configuration, resource bundles,…​ are easy to inject when using CDI and Apache DeltaSpike.

+
+
+

@Exclude annotation: Lets you prevent classes from being treated as CDI beans even if they are in a CDI-enabled +archive in a Java EE 6/CDI 1.0 environment where @Vetoed is unavailable or when you need to veto based on +ProjectStages or expressions.

+
+
+

Scheduling tasks: Async processes in a non-EE7 environment.

+
+
+

Bean Validation integration: Injection of CDI beans and EJBs into Constraint Validators.

+
+
+

BeanProvider: Access the BeanManager and CDI beans even in non-managed classes like JPA 2.0 EntityListeners or +Spring Beans.

+
+
+
+

JSF Improvements

+
+

Multi-window handling: Management of logical windows for batch jobs, browser tab separation in JSF and more.

+
+
+

Type-safe view-config: Lets you bind metadata (e.g. for security) to views with a flexible type-safe approach. It +provides a more solid navigation in case of JSF and helps a lot in the maintenance phase.

+
+
+

View-Controller: Based on type-safe view-configs, view-controller annotations provide a type-safe alternative to +standard tags.

+
+
+

Injection in Converters and Validators: Inject CDI beans and EJBs into JSF Converters and Validators.

+
+
+

JSF event broadcasting to CDI: Allows CDI to be notified about JSF events

+
+
+
+

Productivity Improvements

+
+

Security based on annotations: The foundation for building a robust, capable and non-invasive security solution.

+
+
+

New CDI scopes: TransactionScoped, WindowScoped, ViewScoped, ViewAccess scope, Grouped conversation scope.

+
+
+

Container Control and Test Control: Java SE with CDI, all with a unifying API. Start, stop, add classes to a running CDI container.

+
+
+

Data Module: An out of the box entity framework solution complete with support for container or application managed persistence contexts, as well as JDBC.

+
+
+

Decoupled Exception handling: Event-based exception handling framework, similar to the CDI event observer mechanism.

+
+
+

JMX integration: Any CDI bean can be exposed via JMX easily with a single annotation.

+
+
+

Type-safe i18n messages: Localized messages are easy to use with an interface and a resource bundle, no more boilerplate and your messages now have context within the code.

+
+
+

Type-safe ProjectStages: Compared to ProjectStages in JSF, DeltaSpike provides a type-safe, but still extensible +approach which can be used in CDI-based applications.

+
+
+
+
+
+

Background

+
+
+

CDI

+
+

Java Contexts and Dependency Injection for the Java EE platform (JSR 299), + abbreviated CDI was introduced as part of Java EE 6. The core features of CDI are as follows:

+
+
+
    +
  • +

    improved stateful object lifecycles with an additional context named Conversation that encompasses a series of requests within one session and lifecycle management by the container according to well-defined contexts

    +
  • +
  • +

    dependency injection conducted in a type-safe manner, with type checking conducted at compilation time so errors are exposed earlier and debugging is easier

    +
  • +
  • +

    event notification facility for object interaction

    +
  • +
  • +

    a better approach for interceptors with annotations binding interceptors to objects and with a new interceptor +named decorator that knows about individual bean attributes through inheritance and is more appropriate for use in + solving business problems

    +
  • +
  • +

    a Service Provider Interface (SPI) for developing portable extensions to the CDI container

    +
  • +
+
+
+

CDI is a Java Community Process (JCP) standard. All Java EE 6 compliant +application servers must provide support for CDI. JBoss Weld is a reference +implementation of the CDI specification and other spec-compliant implementations exist such as Apache OpenWebBeans (OWB). While CDI is a Java EE 6 essential, CDI can also be used in Java SE environments with the aid of standalone CDI implementations.

+
+
+
+

Portable CDI Extensions

+
+

The CDI Service Provider Interface (SPI) is exposed to enable extension of the CDI feature set by third parties. +Portable CDI extensions extend CDI implementations and improve existing Java EE APIs by enabling integration of different technologies.

+
+
+

As set out in the CDI specification, a portable CDI extension may integrate with a CDI container as follows:

+
+
+
    +
  • +

    providing its own beans, interceptors and decorators to the container

    +
  • +
  • +

    injecting dependencies into its own objects using the dependency injection service

    +
  • +
  • +

    providing a context implementation for a custom scope

    +
  • +
  • +

    augmenting or overriding the annotation-based metadata with metadata from some other source

    +
  • +
+
+
+

As indicated by the name, portable CDI extensions can be used with any spec-compliant CDI implementation.

+
+
+
+
+
+

Next

+
+
+

For instructions on how to start using DeltaSpike, see Configure DeltaSpike in Your Projects and Enable CDI For Your Java Environment.

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