Java Portlet Specification: Difference between revisions

Revision as of 05:33, 8 September 2018

Revision as of 03:02, 24 September 2018

Line 1:

{{refimprovemore citations needed|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]].

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.

Line 32:

There are many open source and commercial Portlets Catalog available but JSR 168 based solutions are rare.

JSR 168 specifications offer suitability to the developers to reuse the code to maintain a set of JSR 168 compliant portlets. For deployers, it’sit's easy to keep a single set of solution and deploy it on many.

== JSR 286 ==

Line 46:

== JSR 362 ==

'''JSR-362''' is the Java Portlet specification v3.0 and was released in April 2017. <ref>{{cite web | title = JSR 362: Portlet Specification 3.0 | url = https://www.jcp.org/en/jsr/detail?id=362}}</ref> Some of its major features include:<ref>

{{cite web | last = Nicklous | first = Martin (Scott) | title = Portlet Specification 3.0 is Here! | publisher = IBM | date = September 2016 | url = https://static.rainfocus.com/oracle/oow16/sess/1462801563632001pOv8/ppt/JSR362-JavaOne-2016a.pdf }}</ref>

* Resource Dependencies

Line 59:

* [[Web Services for Remote Portlets]] (WSRP)

* Java Portlet Specification

* [[JSR 168| JSR 168 (Java Portlet Definition Standard)]]

== References ==

Line 80:

[[Category:Java specification requests|Portlet specification]]

[[Category:Web portals]]

{{standard-stub}}