The DAO layer will be invoked by a service layer. This layer will use Hibernate API to interact with database. The database will be accessed by a Data Access layer popularly called as DAO Layer. Application Architecture We will have a layered architecture for our demo application. Following is the screenshot of end application.

Display all contacts from contact list.

The basic requirement of the Contact Manager app will be:

Our Goal As describe above, our goal is to create a contact manager application which will allow the user to add a contact or remove it. The list of contacts will be displayed and user will be able to delete existing contacts. The application will be a simple Contact Manager app which will allow user to add new contacts. For this application we will also use Maven for build and dependency management and MySQL as database to persist the data. Make sure that you’re adding the controller to the be.ntroller package, because that’s the location used inside the component scan of the WebConfig.Let us make a complete end-to-end application using Spring 3.0 MVC as front end technology and Hibernate as backend ORM technology.

Speaking of a controller… let’s implement it now we’re busy. This bean is used when defining controllers so that it’s able to resolve the location of the view used inside the controller. Then finally, we also have to create a bean called the getInternalResourceViewResolver() bean. In this case it will be the libs, app and assets folder. The resource handlers are used to indicate which paths should be used to serve static resources. We’re adding the webContentInterceptor() interceptor that allows use to set cache controlling. Our class extends from WebMvcConfigurerAdapter which allows us to add interceptors ( addInterceptors()) and resource handlers ( addResourceHandlers()). Starting from the top again, you can see that we use the #EnableWebMvc annotation to indicate that we’re using Spring Web MVC.

Spring mvc + hibernate todolist app