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

Security context


The security context object is used to programmatically check a user's authority to access a specific resource. This is very useful when you need to do some custom behavior upon having an invalid request from the user, rather than the default one specified by the security API.

In the following example, we're going to forward the user to another page if, and only if, they have access to this page:

@WebServlet("/home") 
public class HomeServlet extends HttpServlet { 
 
    @Inject 
    private SecurityContext securityContext; 
 
    @Override 
    protected void doGet(HttpServletRequest req, HttpServletResponse 
    resp) 
            throws ServletException, IOException { 
  if (securityContext.hasAccessToWebResource("/anotherServlet",  
  "GET")) { 
         req.getRequestDispatcher("/anotherServlet").forward(req, 
         res); 
        } else { 
            req.getRequestDispatcher("/logout").forward(req, res); 
        } 
    } 
} 

As you can see, we have used the CDI's...