This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Software Teaming: A Mob Programming, Whole-Team Approach and have Woody Zuill and Kevin Meadows on-line! See this thread for details.
I am develop a large project using spring 3.0 and hibernate 3.0 technology in that i have use @controller class but my application is web based and no of process and billing generation process i am use in a application. so my problem is that how many @controller class is use in my project or only one @controller class is required for whole application project.
Since your Controllers will be POJOs, with no implements on Spring MVC interfaces, then it really is about what makes the most sense to you and your team. It ends up being the same questions as to what should all be in the same class, and what should not regardless of Spring or MVC.
Meaning if you have one Controller with hundreds of methods in it, then it is too big, too unmaintainable. But you don't want a hundreds of Controllers each with only one method in it.