Java Reference
In-Depth Information
Concurrency utilities for Java EE 1.0 - JSR 236
Concurrency utilities is a new feature pack to use multithreading in Java EE application
components. The new specification provides
ManagedExecutorService
(a
container-aware version of
ExecutorService
known from Java SE), which can be
used to delegate the execution of tasks to a separate thread. These managed tasks could
use most of the features that are available for application components (such as EJBs or
Servlets). It is also possible to schedule cyclic or delayed tasks using new
Man-
agedScheduledExecutorService
. These new additions to the platform are filling
a functional gap for Java EE, which was very hard to overcome within its architecture
earlier on.
Batch applications for the Java Platform 1.0 - JSR 352
Batch jobs were another area of enterprise application development, which was not
covered by earlier versions of Java EE. The new batch processing framework is used to
provide a common solution to run tasks that are executed without user interaction. Java
EE provides the developer with the following options:
• Batch runtime for the execution of jobs
• A job description language (based on XML)
• The Java API for the implementation of the business logic for the batch tasks
• jBeret, which is the batching framework used in WildFly
Java API for JSON Processing 1.0 - JSR 353
Java EE 7 now comes with out-of-the-box JSON processing, so the developer is no longer
forced to use external libraries for this task. The new API allows JSON processing to use
two approaches: object model (DOM based) and streaming (event-based).
Java API for WebSocket 1.0 - JSR 356
To fully support the development of applications based on HTML5, Java EE 7 requires a
standardized technology for two-way communication between the server and the user's
browser. The WebSocket API allows the developer to define server-side endpoints, which
will maintain a TCP connection for every client that will connect to them (using, for in-
stance, a JavaScript API). Before the new specification, developers had to use vendor-spe-
cific libraries and not portable solutions to achieve the same goal.
