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?
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?
very nice explaination buddy. i liked the way you put your problem.
anyways. it is not necessary in MVC that you have to have one servlet only. we can use task/module specific servlets. in MVC the Model(your business logic) and your View(presentation tier) should not interact with each other directly. they should go through a controller. a Controller could be any servlet.
But here, in your previous message, i can not hear anything about the Model. how you are implementing your model. usually, if not using something like ejb or something, our simple java classes work as a Model.
JSP ---> servlet(could be any, if many) ----> java class (business logic)
java class (business logic) ----> servlet(could be any, if many) ---> JSP
I hope it will give you some idea about how MVC works.
Joined: Jul 03, 2002
I also have some simple classes (models) that are carrying out some tasks. I am calling the methods in these classes from the servlets based on certain conditions that I check in the servlets. So if a condition is tru the servlet calls method "a" in the class else it calls method "b" etc.
My only worry was I was ending up with quite a few servlets (about 10) and I thought this may not be correct.
Thanks for clearing this.
Joined: Aug 15, 2004
why are you thinking like that. it is OK. sometimes we use only one servlet as a controller in the whole app.
Can i get a model code for the MVC2 architecture. Jsut to get the full taste of it?
Any code, simple, like one for each component, in a model, View and controller.....
This will really be helpful.
Joined: Aug 15, 2004
Yeah i have some code but its proprietry. Dont have something of my own. So it is impossible to send or disclose it anyway.
but you can get the simple example codes easily from any MVC2 tutorials. if we look at struts framework, it reflects MVC architecture + Command Pattern. And most of the Servlet and JSP books talk about design patterns, primarily MVC2.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com