You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/src/main/asciidoc/overview.adoc
+7-13Lines changed: 7 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,20 +23,17 @@ the most from this technology.
23
23
24
24
*Transactional support for non-EJB beans:* The Transactional Interceptor in DeltaSpike paved the way for
25
25
`@Transactional` in Java EE 7.
26
-
27
-
*Injectable Servlet objects:* Enables CDI injection in Servlets in Java EE 6/CDI 1.0 environments
26
+
Although we not only support JTA transactions but also resource local transactions and use a slightly different Exception handling.
28
27
29
28
*Injectable resources:* Configuration, resource bundles,... are easy to inject when using CDI and Apache DeltaSpike.
30
29
31
30
*@Exclude annotation:* Lets you prevent classes from being treated as CDI beans even if they are in a CDI-enabled
32
-
archive in a Java EE 6/CDI 1.0 environment where `@Vetoed` is unavailable or when you need to veto based on
33
-
ProjectStages or expressions.
34
-
35
-
*Scheduling tasks*: Async processes in a non-EE7 environment.
31
+
archive in a Jakarta EE project.
32
+
You can even exclude classes based on ProjectStages or configuration expressions.
36
33
37
-
*Bean Validation integration:* Injection of CDI beans and EJBs into Constraint Validators.
34
+
*Scheduling tasks*: handle Async processes in a non-JakartaEE environment.
38
35
39
-
*BeanProvider:* Access the BeanManager and CDI beans even in non-managed classes like JPA 2.0 EntityListeners or
36
+
*BeanProvider:* Easy Access to the BeanManager and CDI beans even in non-managed classes like JPA 2.0 EntityListeners or
40
37
Spring Beans.
41
38
42
39
@@ -50,8 +47,6 @@ provides a more solid navigation in case of JSF and helps a lot in the maintenan
50
47
*View-Controller:* Based on type-safe view-configs, view-controller annotations provide a type-safe alternative to
51
48
standard tags.
52
49
53
-
*Injection in Converters and Validators:* Inject CDI beans and EJBs into JSF Converters and Validators.
54
-
55
50
*JSF event broadcasting to CDI:* Allows CDI to be notified about JSF events
56
51
57
52
=== Productivity Improvements
@@ -64,8 +59,6 @@ standard tags.
64
59
65
60
*Data Module:* An out of the box entity framework solution complete with support for container or application managed persistence contexts, as well as JDBC.
66
61
67
-
*Decoupled Exception handling:* Event-based exception handling framework, similar to the CDI event observer mechanism.
68
-
69
62
*JMX integration:* Any CDI bean can be exposed via JMX easily with a single annotation.
70
63
71
64
*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.
@@ -77,7 +70,8 @@ approach which can be used in CDI-based applications.
77
70
78
71
=== CDI
79
72
Java Contexts and Dependency Injection for the Java EE platform (link:https://jcp.org/en/jsr/detail?id=299[JSR 299]),
80
-
abbreviated _CDI_ was introduced as part of Java EE 6. The core features of CDI are as follows:
73
+
abbreviated _CDI_ was introduced as part of Java EE 6 and is now part of Jakarta Enterprise.
74
+
The core features of CDI are as follows:
81
75
82
76
* 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
83
77
* dependency injection conducted in a type-safe manner, with type checking conducted at compilation time so errors are exposed earlier and debugging is easier
0 commit comments