Originally posted by Phil Chuang:
I guess I'm coming from the viewpoint where I'm using the controller more for application flow than mere URL->servlet flow. My current project is being designed such that there is one "controller" servlet per application. It has an instance of a POJO (Plain Old Java Object) controller, and based on params, it determines which workflow to call (more POJOs). Instead of having multiple servlets, I have one servlet and multiple POJOs. So my controller at the java application level and not the servlet level.
Originally posted by Manas Ahlaad:
Why should a controller be a servlet , why not a JSP ? why is it mentioned in all the framesworks like Structs, MVC that servlet is controller.
Originally posted by Gregg Bolinger:
I just like plain old Servlets used the way J2EE is designed. Take a request and forward it, or send a response. It doesn't get any simpler.
Originally posted by Kenneth Robinson:
This, in a very small nutshell, is everything you need to know about the basics of web applications.
I could (and have) go on for hours about why I think so, but that is not what this thread is about.
It's just that putting any sort of business logic in a jsp is not the en vogue thing to do nowadays