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

Modules

A module is a library with its own life cycle. By default, a module is started at the start of WildFly and stopped at the stop of WildFly. A module is loaded in a lazy mode only when it is required by an application.

WildFly loads the dependencies with the following priorities:

  • Libraries inside the application
  • Modules
  • Libraries inside other external applications

JBoss module 1.5.2.Final is the product managing the modules in WildFly. All WildFly dependencies are modules, and they are situated in the modules/system/layers/base folder. Now, let's see an example of a module representing hibernate.

From the modules folder, there is the org/hibernate/5.0/module.xml descriptor file. The following is the content to transform the hibernate library into a module:

<module-alias xmlns="urn:jboss:module:1.3" name="org.hibernate" slot="5.0" ...