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

Job context and step context

Batches provide two contexts: job context, which provides information about the current job (called also process) execution, and step context, containing informations for the single step of the job. The common properties for both the job context and the step context are as follows:

  • Transient user data: A transient data object belonging to the current Job XML execution element.
  • Properties: The properties propagated by the client. They will be always in the job and in the steps.
  • Name: Name of the job or step described in the JSL.
  • Execution id: Identifier for the current job or step. Identifiers are different for more jobs or more steps.
  • Batch status: The status of the execution. Refer to the Batchlets section for more details.
  • Exit status: A variable used to decide the direction of the flow; it is custom.

The other property of the job context is the...