I posted this in the design
patterns forum a couple of days ago but got no reply. Perhaps put it in the wrong forum?
"I am developing a sample web application using the Model view controller pattern. I have a handlerServlet which I use to pass control to other
servlets. Those servlets contain some of my business logic and in turn pass control to JSPs for display. Like depicted below
handlerServLet --> Task specific servlets --> JSPs (results / user inputs)
Now, based on certain user inputs I need to forward the user from the JSPs to some other servlets. I reckon this is going to get me into a bit of a mess.
Is it alright that I pass the control back to the handlerServlet and then go to the respective servlet from there? On the other hand, isn't it a bit of an extra overhead when the control can go direct from the
JSP to another servlet?
This is the dilemma I am facing. Can someone advise?
Also should I make a servlet for each business logic task that I want to perform? Or should I just have a new method in my handlerServlet?
Thanks. "
Can someone pls also explain whether MVC requires that you have a single controller servlet. What if it becomes too unweildy? Can we have multiple controller servlets co-ordinating?
Thanks again.