Book Image

Spring 5.0 Cookbook

By : Sherwin John C. Tragura
Book Image

Spring 5.0 Cookbook

By: Sherwin John C. Tragura

Overview of this book

The Spring framework has been the go-to framework for Java developers for quite some time. It enhances modularity, provides more readable code, and enables the developer to focus on developing the application while the underlying framework takes care of transaction APIs, remote APIs, JMX APIs, and JMS APIs. The upcoming version of the Spring Framework has a lot to offer, above and beyond the platform upgrade to Java 9, and this book will show you all you need to know to overcome common to advanced problems you might face. Each recipe will showcase some old and new issues and solutions, right from configuring Spring 5.0 container to testing its components. Most importantly, the book will highlight concurrent processes, asynchronous MVC and reactive programming using Reactor Core APIs. Aside from the core components, this book will also include integration of third-party technologies that are mostly needed in building enterprise applications. By the end of the book, the reader will not only be well versed with the essential concepts of Spring, but will also have mastered its latest features in a solution-oriented manner.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Creating a multi-action @Controller


The implementation of the multi-action controller has evolved from extending the class org.springframework.web.servlet.mvc.multiaction.MultiActionController up to the modern day use of the @Controller annotation. This recipe will show you how to easily create a multi-action controller using JavaConfig.

Getting started

We will be adding a multi-action controller to the same project, ch03. This is another option to manage all the request handlers.

How to do it...

To create a multi-action controller in the Spring 5.0 platform, follow these steps:

  1. Let us start this recipe with a multi-action controller named MultiActionController with all its handler methods mapped to their respective URLs, similar to a hub of independent services:
@Controller 
public class MultiActionController { 
 
  @RequestMapping(value={"/send/*", "/list/*"}, 
    method=RequestMethod.GET) 
  public String defaultMethod(){ 
    return "default_msg"; 
  } 
  
  @RequestMapping(value="/send/message_get...