Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

[Portlet 1] Design considerations compared to plain servlet/jsp

 
Jesus Angeles
Ranch Hand
Posts: 2068
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

If we have a big application that we will run on a portlet, how are we going to design it, considering that there is only one portlet, and many servlets/jsps on the application? Is it almost a requirement to use an MVC framework like struts or jsp, otherwise, it will be almost impossible to make a clean implementation of a big application?

Or are their other design patterns for the portlet scenario?
 
Bigwood Liu
Ranch Hand
Posts: 240
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are lots of things need to be consider before you start a new "big" application.

1. The first thing is to set the boundary of your application. What you will do, what you will not do. Do not try to add everything at the first time when you build your application. Otherwise it will take forever. Create what is needed and build it little by little.

2. Use MVC. Choose JSP/JSF/Struts which ever you are familiar with. Generally speaking, JSF/Struts will save you time and force you to use MVC, which is a very good practice. Bad side is if you need time to get familiar with it, and sometimes if there are some functions that the frameworks do not provide, it might take you more time to implement it. Plus if there are errors, it is difficult to debug.

3. Design database tier. Add DAO or Database facade if necessary to decouple your application from database.
 
Jesus Angeles
Ranch Hand
Posts: 2068
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In addition to that, Spring MVC Portlet may avoid reinventing the wheel.
 
saumil baxi
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One small Thing dont try to build your complete application in just one portlet. Try to break it down business wise or functionality wise. So that you can reuse them any where you want.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic