I'm assuming you have an architecture like this: TodoController ==> TodoService ==> TodoDao.
If so, TodoController should handle all CRUD operations on your Todo entity. Why would you have another controller that performs CRUD operations on the Todo entity?
If you DID have another controller that performed CRUD operations on the Todo entity, that controller could still use the TodoService and TodoDao layers; eliminating the need for duplicate code.
I get the feeling you are looking for a 'Spring-based' solution to your problem in order to learn Spring, but based on your requirements, a database trigger on the Todo table may be more appropriate.