Not to display the data on the way I have made some series of changes on the back in project as well.
I was just given high level interaction of the changes that I have done.
So there is no change inside the project security conflict, which is related to spring security configuration
that changes our bill controllers for each and every service that we have to build, like account balance
card, like if you see Godse controller.
So this is the service that will invoke from the way after login and authentication is successful and
this controller will call the repository associated with the card.
So called repository is a repository that is associated with the card table and you can see easily.
So this is the interface which extends great repository from Spring Data JPA and the entity that it
is cut.
Go and look into the card is an entity which is associated to your table cards and these are all the
columns present inside the card stable.
So this is a simple Jobster based upon the customer.
I am trying to get all the cards and if the cards is not null, I'm returning the list of cards to the
EU which will be displayed on the screen.
Otherwise I'll just personal value.
The same applies for other controllers.
Also like launch controller, launch controller has a launch repository which is associated with an
entity launch and based upon the customer 80 be getting all the loans with that customer and pass through
the UI.
So this is how that changes happen on the controller and the repository.
And at the same time, I also created model classes for each and every entity associated with the new
webpages.
Like all these annotations are from the AP like Entity Table column.
And at the same time, I'm also updated.
The script starts with the latest table details.
So previously we only have customer table with the login credentials details.
But now I have created the tables for each and every functionality that we have inside our application
like account account transactions and the records and loans, loans, records, cards, cards, records.
And at the same time we also have notices and contacts misses table for storing the contacts inside
our database.
So with this, I'm assuming you are understanding the code that we have done both on the way and backend.
So don't worry if something is not clear, because we will discuss more and more in the coming videos
and in the next video will make our backend application up and try to contact from the UI and see what
is happening.
Thank you.
And see you in the next by.