Java Portlet Specification: Difference between revisions

Revision as of 15:21, 7 October 2018

Revision as of 05:34, 15 October 2018

Line 8:

Some examples of portlet applications are [[e-mail]], [[weather forecasting|weather reports]], [[discussion forum]]s, and [[news]].

A portlet is managed by a [[portlet container]]. Portlet standards platform independent [[application programming interface]]s that are intended to enable [[software developer]]s to create portlets that can be [[plug-in (computing)|plugged into]] any portal supporting the standards. An example is the [[Java Portlet Specification]]. A Java portlet resembles a Java [[Servlet]], but produces fragments rather than complete documents, and is not bound by a URL.

A '''portlet container''' runs [[portlet]]s and provides them with the required runtime environment. A portlet container contains portlets and manages their life cycles. It also provides persistent storage mechanisms for the portlet preferences. A portlet container receives requests from the portal to execute requests on the portlets hosted by it. A portlet container is not responsible for aggregating the content produced by the portlets; the portal itself handles aggregation. A portal and a portlet container can be built together as a single component of an application suite or as two separate components of a portal application.