• Post Reply Bookmark Topic Watch Topic
  • New Topic

A question of design/usual practice in MVC

 
Val Pecaoco
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I'm implementing an Intranet portal in MVC whereby the services share single sign-on. I have just finished the first service and I'll be putting in the next one in a couple of days (with another not far behind). The first service has one controller servlet; should I also use this as the controller servlet for the second service or should I create another servlet? Actually this is more like an issue in large-scale design and I would really be appreciative for all the help.
Ex Animo Java!
-- Val
 
Tim Holloway
Bartender
Posts: 18412
58
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you use a framework like Struts, not only is there a single servlet, but it's already prewritten and debugged for you.
True "MVC" isn't possible under HTTP because the components don't bind tightly enough. The popular design pattern these days for servlet/JSP programming is known as Model 2.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!