Originally posted by neha singla: hi, well am looking for the features for this project
Are you going to build a generic portal or a specific portal? Some of the features I would like to suggest: (You may skip some of them) Portal Administration Content Management User registrations and management Configurable Portal Settings Email and news-letters sub-system Forums Surveys Search engine Help system Online Payment I suggest you to go thru following link for comprehensive info on portals http://www.sapdesignguild.org/editions/edition3/generic_pages.asp [ September 22, 2003: Message edited by: Murthy Narasimha ]
Interesting link, thanks! Growing a taxonomy of information like that will increase the odds of any two people using the same word for the same thing. I didn't think the article said anything to distinguish a portal from any other web site or application. What defines a portal to you? Portal products seem to be about gathering information from multiple sources into one set of pages, maybe about putting those pages in small viewports and composing a larger page of multiple viewports. What I'm admitting in a roundabout way is that I don't know what requirements of a "portal" would not be met by a fairly conventional front-controller architecture. Anybody?
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Neha, In your very first post, you mentioned that you know JSP,Servlets,Java etc at a basic level, which probably means that you know how the syntax and you have the ability to understand a simple Servlet's or a JSP functionality's. So, what you probably want to know now is how to put all these things together so as to actually build something from whatever you have learnt. So, if my above understanding is correct, I would suggest a few ideas of how to go about it. 1) If you have any books on these technologies(like Java Server Programming), you will see that most of them will have a case study in the end, which demonstrate how to apply these technologies into a demo application.You can learn from this. 2) There is a very good case study,of how to use the technologies in J2EE on http://java.sun.com. It's called "PetStore" and as the name suggests it is an online PetStore application.You can ignore EJB and Webservices that are also part of this application for the time being. You can dowload everything related to this app and study how it was built. 3)Any webserver or Appserver that you are using or going to use will contain lots of examples which will give you valuble insight on the threads that become a part of a robust application. You can also make use of these examples. And most importantly,before you actually start coding, prepare a small design document which documents how you are going to go about developing this application.This way, you will know what functionality needs to be captured in which component. Hope this helps, Manjunath [ September 23, 2003: Message edited by: Manjunath Subramanian ] [ September 23, 2003: Message edited by: Manjunath Subramanian ]