• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Portlets vs Servlets

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
May be one of you over there might help...

i could understand what's the difference between the portal server apps and servlet-jsp apps.. but i still couldn't get the difference, why they came into existence..

also which is ruling now... cgi,jsp-servlet, or portlets....

help out pals
 
Veeramanikandan Radhakrishnan
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
also, there are still servlet-jsp in usage even though portlets came to existence...

why?

i think someone could make out!!!
 
author and cow tipper
Posts: 5006
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The big different between Servlets and Portlets is the focus.

A Servlet/JSP application, in very general terms, controls most of the overall page delivered to a client. With a portlet, the content delivered makes up only a very small section of the overall page. This allows a great division of labour when developing the overall website - things such as themes, skins, layout, user rights, etc, can all be configured outside and away from the actual portlet application - things that are a bit more difficult, although not impossible to do, with a typical Servlet/JSP application.

The JSR168 portlet API does not replace the Servlet/JSP API, but instead, sorta builds on top of it. Look at the various objects in the Portlet API here: All of the Classes in the JSR168 Portlet API Most of those classes are just wrappers for Servlet/API classes. In fact, I think the docs actually say that a portlet container sits on top of a Servlet/JSP container.

A portal server is a great product that fits a big need that many clients require, and it can provide customization, personalization, user rights management and content management features that integrate and can be used quite easily. For many customers, a portal isn't a perfect fit, but for many others it is, and when it is, it's amazing.



Cheers!

-Cameron McKenzie
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic