Book Image

Building Web Apps with Spring 5 and Angular

By : Ajitesh Kumar Shukla
Book Image

Building Web Apps with Spring 5 and Angular

By: Ajitesh Kumar Shukla

Overview of this book

Spring is the most popular application development framework being adopted by millions of developers around the world to create high performing, easily testable, reusable code. Its lightweight nature and extensibility helps you write robust and highly-scalable server-side web applications. Coupled with the power and efficiency of Angular, creating web applications has never been easier. If you want build end-to-end modern web application using Spring and Angular, then this book is for you. The book directly heads to show you how to create the backend with Spring, showing you how to configure the Spring MVC and handle Web requests. It will take you through the key aspects such as building REST API endpoints, using Hibernate, working with Junit 5 etc. Once you have secured and tested the backend, we will go ahead and start working on the front end with Angular. You will learn about fundamentals of Angular and Typescript and create an SPA using components, routing etc. Finally, you will see how to integrate both the applications with REST protocol and deploy the application using tools such as Jenkins and Docker.
Table of Contents (18 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Introduction to NamedQuery and Criteria


Before we go on to understand some of the common hibernate operations, let's look into what NamedQuery and Criteria API are. This concept will be referred in the next section for performing data retrieval operations.

What is NamedQuery?

NamedQuery in Hibernate is a way to provide alias names to one or more queries, which are static in nature. The primary coding problem that gets solved with NamedQuery is the queries lying all around, and thus, gets difficult to manage. NamedQuery allows queries to be segregated at one place and accessed later via alias names. They are parsed/prepared once, and are thus considered as more optimal than other query mechanisms such as Criteria. NamedQuery can be defined using annotation or mapping files. In this section, we shall take a look at examples using NamedQuery and related annotations.

The following are some of the key annotations in relation with NamedQuery:

  • @NamedQuery: This is used to define a Java Persistence...