Book Image

Mastering Spring MVC 4

By : Geoffroy Warin
Book Image

Mastering Spring MVC 4

By: Geoffroy Warin

Overview of this book

<p>Spring MVC is the ideal tool to build modern web applications on the server side. With the arrival of Spring Boot, developers can really focus on the code and deliver great value, leveraging the rich Spring ecosystem with minimal configuration.</p> <p>Spring makes it simple to create RESTful applications, interact with social services, communicate with modern databases, secure your system, and make your code modular and easy to test. It is also easy to deploy the result on different cloud providers.</p> <p>Mastering Spring MVC will take you on a journey from developing your own web application to uploading it on the cloud.</p> <p>You begin by generating your own Spring project using Spring Tool suite and Spring Boot.</p> <p>As you develop an advanced-level interactive application that can handle file uploads as well as complex URLs, you will dive into the inner workings of Spring MVC and the principles of modern web architectures.</p> <p>You will then test, secure, and optimize your Spring web application and design RESTful services that will be consumed on the frontend.</p> <p>Finally, when everything is ready, you will release your application on a cloud provider and invite everyone to see.</p>
Table of Contents (17 chapters)
Mastering Spring MVC 4
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Generating XML


RESTful APIs sometimes return responses in different media types (JSON, XML, and so on). The mechanism responsible for choosing the correct media type is known as content negotiation in Spring.

By default, in Spring MVC, the ContentNegotiatingViewResolver bean will be in charge of resolving the correct content according to the content negotiation policies defined in your application.

You can have a look at ContentNegotiationManagerFactoryBean to see how these policies are applied within Spring MVC.

Content type can be resolved with the following strategies:

  • According to the Accept header sent by the client

  • With a parameter such as ?format=json

  • With a path extension such as /myResource.json or /myResource.xml

You can customize these strategies in your Spring configuration by overriding the configureContentNegotiation() method of the WebMvcConfigurerAdapter class.

By default, Spring will use the Accept header and the path extension.

To enable XML serialization with Spring Boot, you...