Java Portlet Specification: Difference between revisions

Revision as of 18:31, 31 March 2018

Revision as of 05:33, 8 September 2018

Line 1:

{{refimprove|date=January 2013}}

The '''Java Portlet Specification''' defines a [[design by contract|contract]] between the [[portlet container]] and [[portlet]]s and provides a convenient programming model for Java portlet developers.

'''Portlets''' are [[Pluggable look and feel|pluggable]] [[user interface]] [[software component]]s that are managed and displayed in a [[web portal]], for example an [[enterprise portal]] or a [[web CMS]]. A portlet can [[Web aggregator (disambiguation)|aggregate]] (integrate) and personalize content from different sources within a web page. A portlet responds to requests from a web client with and generates dynamic content.

Portlets produce fragments of [[markup language|markup]] ([[HTML]], [[XHTML]], [[wireless markup language|WML]]) that are aggregated into a portal. Typically, following the [[desktop metaphor]], a portal page is displayed as a collection of non-overlapping portlet windows, where each portlet window displays a portlet. Hence a portlet (or collection of portlets) resembles a [[web-based application]] that is hosted in a [[Web portal|portal]].

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.

== JSR 168 ==