Is this the right approach for Controller-Service-Dao implementation?
There are various implementations of MVC or MVC inspired patterns, there aren't hard and fast rules to follow, each implementation is often tweaked to suit certain needs.

Here are some old threads that explain the responsibility of each layer and may answer some of your questions:


  Is this the right approach for Controller dao service pattern?


MVCS - Model View Controller Service

Responsibilities and use of Service and DAO Layers


  Purpose of service class , is it for redirection only to dao or for validations also?


Service layer vs DAO — Why both?

In MVC , DAO should be called from Controller or Model


  Do we need to use inheritance for Dao classes ?


Most effective way to reflect inheritance relationship in DAOs?