Book Image

Spring Essentials

Book Image

Spring Essentials

Overview of this book

Spring is an open source Java application development framework to build and deploy systems and applications that run on the JVM. It is the industry standard and the most popular framework among Java developers with over two-thirds of developers using it. Spring Essentials makes learning Spring so much quicker and easier with the help of illustrations and practical examples. Starting from the core concepts of features such as inversion of Control Container and BeanFactory, we move on to a detailed look at aspect-oriented programming. We cover the breadth and depth of Spring MVC, the WebSocket technology, Spring Data, and Spring Security with various authentication and authorization mechanisms. Packed with real-world examples, you’ll get an insight into utilizing the power of Spring Expression Language in your applications for higher maintainability. You’ll also develop full-duplex real-time communication channels using WebSocket and integrate Spring with web technologies such as JSF, Struts 2, and Tapestry. At the tail end, you will build a modern SPA using EmberJS at the front end and a Spring MVC-based API at the back end.By the end of the book, you will be able to develop your own dull-fledged applications with Spring.
Table of Contents (14 chapters)
Spring Essentials
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

The motivations behind SPAs


We know that Spring mainly focuses on the server side, that is, the integration, service, and data layers. Spring relies on other web technologies for rendering the presentation layer. Although Spring MVC does facilitate the presentation layer with the help of web technologies such as JSP and Thymeleaf, all of them work based on server-side rendering and full-page refreshes for responding to user interactions. In this traditional approach, the presentation layer of a web application is composed of a bunch of totally independent HTML files served by a server on demand, each representing a single screen, with just one rendered to the client browser at a time, taking a full round trip to the server for each user interaction. This provides a very poor user experience compared to native desktop applications, which gracefully re-render just the specific parts of the screen when required.

Although you can use some AJAX-using frameworks such as jQuery, in order to get...