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

The JMS context

A JMS context is the main interface in the simplified JMS API introduced for JMS 2.0. This adds the functionality of two different objects from the JMS 1.1 API--a connection and a session in a single object.

When an application needs to send messages, we need to use the createProducer method to create a JMSProducer, which provides methods to configure and send messages. Messages may be sent either synchronously or asynchronously.

When an application needs to receive messages, we need to use one of the several createConsumer or createDurableConsumer methods to create a JMS consumer . A JMS consumer provides methods to receive messages either synchronously or asynchronously.

According to the JMS 1.1 API, a JMS context should be thought of as representing both a connection and a session. Although the simplified API removes the need for applications to use those objects...