> -----Original Message----- > From: Jason Novotny [mailto:novotny@;aei.mpg.de] > Sent: Tuesday, October 29, 2002 12:11 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: why do portlets inherit from servlets? > > > Hi, > > I've been looking at IBM's Portlet API in which portlets inherit from > servlets-- I would like to get some technical reasons for why this is a > good or bad idea. For one thing it seems performance might be slower > since portlets would be invoked presumably using > RequestDispatcher.include() methods rather than using a portlet object > instance. Another thing is that portlets would be managed by the > servlet container such as classloading, whereas if I have portlets as > independent objects I could use my own classloading mechanisms to > reload them without restarting the servlet container. > Any comments and information is greatly appreciated. >
The advantage is that you can leverage the Servlet API with your portlets, instead of mimicking the functionality. This makes for a nice aggregation engine based on servlet dispatcher, all built in and less work for the portlet container developers. I wouldn't consider IBM's API as the standard, especially in this area of portlets inheriting from servlets. -- To unsubscribe, e-mail: <mailto:jetspeed-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-dev-help@;jakarta.apache.org>
