Book Image

Developing Middleware in Java EE 8

Book Image

Developing Middleware in Java EE 8

Overview of this book

Middleware is the infrastructure in software based applications that enables businesses to solve problems, operate more efficiently, and make money. As the use of middleware extends beyond a single application, the importance of having it written by experts increases substantially. This book will help you become an expert in developing middleware for a variety of applications. The book starts off by exploring the latest Java EE 8 APIs with newer features and managing dependencies with CDI 2.0. You will learn to implement object-to-relational mapping using JPA 2.1 and validate data using bean validation. You will also work with different types of EJB to develop business logic, and with design RESTful APIs by utilizing different HTTP methods and activating JAX-RS features in enterprise applications. You will learn to secure your middleware with Java Security 1.0 and implement various authentication techniques, such as OAuth authentication. In the concluding chapters, you will use various test technologies, such as JUnit and Mockito, to test applications, and Docker to deploy your enterprise applications. By the end of the book, you will be proficient in developing robust, effective, and distributed middleware for your business.
Table of Contents (18 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Chapter 7. Communicating with Different Systems with JMS 2.0

In this chapter, we are going to discuss the Java Messaging System (JMS) 2.0 API, which provides a full-featured implementation of Message-oriented middleware (MOM) in Java. If you are new to the message-oriented middleware concept, or have never used one of them before, don't worry; we are going to explain the basic concepts of messaging and JMS in the next sections.

You will learn how to use JMS 2.0 to send messages from any Java EE component to be consumed by Message-driven beans (MDB) asynchronously and concurrently. Note that the concept of messaging here is completely different from emails; emails are meant for communication between two or more persons, while messages in MOM are meant for communication between two or more software components. Emails contain some arbitrary information to be read by humans, while MOM messages are structured information to be processed by some piece of software; this information represents some...