Book Image

Mastering Java EE Development with WildFly

By : Luca Stancapiano
Book Image

Mastering Java EE Development with WildFly

By: Luca Stancapiano

Overview of this book

Packed with rich assets and APIs, Wildfly 10 allows you to create state-of-the-art Java applications. This book will help you take your understanding of Java EE to the next level by creating distributed Java applications using Wildfly. The book begins by showing how to get started with a native installation of WildFly and it ends with a cloud installation. After setting up the development environment, you will implement and work with different WildFly features, such as implementing JavaServer Pages. You will also learn how you can use clustering so that your apps can handle a high volume of data traffic. You will also work with enterprise JavaBeans, solve issues related to failover, and implement Java Message Service integration. Moving ahead, you will be working with Java Naming and Directory Interface, Java Transaction API, and use ActiveMQ for message relay and message querying. This book will also show you how you can use your existing backend JavaScript code in your application. By the end of the book, you’ll have gained the knowledge to implement the latest Wildfly features in your Java applications.
Table of Contents (20 chapters)
5
Working with Distributed Transactions
16
WildFly in Cloud

Batches and Workflows

One good feature that started in Java EE7 is batch management. WildFly supports the implementation of this specification, the JSR 352 batch applications for the Java platform started in the 2011 and now finally integrated into the Java EE specifications.

A batch is a group of records processed as a single unit, usually without input from a user. Batches are important things for the applications because customers need the option to execute scheduled asynchronous operations for example massive data to update automatically for a date in the night.

Batches can be compared to the scheduled singletons seen in Chapter 11, Asynchronous EJB but they are organized with one scope in mind, guaranteeing the process of a large quantity of data. So the batches work in a domain different to the EJB because they don't need to be called upon by an external component....