Java technology based webcomponent Managed by a portal container
Generates a piece of markup called“fragment”
–Adheres to certain rules such as no <html> tags, fornstance
–Fragment generated by a Portlet aggregates with that from other Portlets to form a portal page
–Fragment generated by a Portlet may vary from one user to another depending on the user configuration
Why Portlets?
Servlet architecture does not define the Desktop metaphor where markup aggregation can occurr.
Servlet architecture does not define the possible states and transitions of an included Servlet or JSP
Servlet architecture does not define how the state of one Servlet or JSP affects the display of the other included Servlets or JSPs
Servlet architecture does not define a personalization interface nor the idea of persisting the personalization information
Servlet architecture does not define URL-rewriting functions to allow the creation of links and actions targeted to a specific form within the fragment of a page (Portletmarkup fragment)
Servlet architecture does not support caching scheme of fragments
Portlet vs. Servlet(Portlet is built overServlet Architecture)
Both are Java technology based web components
Life-cycle is managed by a specialized container
–Servlet by servlet container
–Portlet by portlet container
Both generate dynamic content
Both interact with web client via a request/response paradigm
Deployment model
Classloading
Packaging and deployment
Lifecycle management
Session management
Request dispatching
Differences from Servlet
Portlets only generate markup fragments, not complete documents
Portlets arenot directly bound to a URL
Web clients interact with portlets through a portal system
Portlets have a more refined request handling
-action requests and render requests
Portlets have predefined states
–portlet modes and window states
Portlets can exist many times in a portal page.
Extra Features of Portlets:
Portlets have means for accessing and storing persistent configuration and customization data
Portlets have access to user profile information
Portlets have URL rewriting functions for creating hyperlinks within their content
–allow portal server agnostic creation of links and actions in page fragments
Portlets can store transient data in the portlet session in two different scopes
–application-wide scope
–the portlet private scope
No comments:
Post a Comment