if i get the MVC architecture correctly: would it be correct if i say that: let's say there could be some jsp pages with only 1 servlet controller and a couple of beans in a module. let's put it that my application consists of modules. that means i have at least 1 servlet controller for each of my module.
"True" MVC was designed for an environment where the components are much more tightly connected than HTTP allows. Among other things, HTTP doesn't permit the controller to modify the view after it was sent nor for a view to talk back to the controller without being completely replaced (I'm talking web pages, not HTTP tunneling here, BTW). Some quite usable paradigms have been made after the fashion of MVC that DO work in the HTTP world, such as Model 2. And this points out the value of using Patterns as guides vs. ironclad Rules. If you avoid dogmatism, you can adapt a pattern to make you more productive, thence creating a new pattern. If you look at Patterns as immutable Law, you'll end up choking on your own narrow orthodoxy.
An IDE is no substitute for an Intelligent Developer.