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

What are web services?


Web services are functions that are deployed on one server and can be called remotely from any other system. Calling functions remotely is not something new, it was always a primary concept in building distributed systems. Dozens of methodologies and protocols were invented to support remote function calling—CORBA, IIOP, DCOM, and many other technologies are good examples of the idea. However, web services have gained popularity and domination over all of those, and we will soon show why.

The basic idea of web services is very simple, and can be summarized in three steps:

  1. You write a function
  2. You deploy the function on a web server
  3. You assign the function a unique URL

For example, if you need to use a function that lists a set of products of another system, you may write this function, deploy it on some server, and give it the following URL: http://example.com/products.

If you open this URL in a web browser, you should see a list of all available products. It's very similar...