Java Portlet Specification: Difference between revisions

Revision as of 00:41, 13 February 2024

Latest revision as of 14:18, 21 March 2024

(7 intermediate revisions by 4 users not shown)

Line 1:

{{Short description|Technical standard}}

{{more citations needed|date=January 2013}}

A '''Java Portlet Specification''' ('''JSR''') defines a [[design by contract|contract]] between [[Portlet|portlets]] and their [[Portlet container|containers]]; they provides a convenient [[programming model]] for Java portlet developers. '''Portlets''' are [[PluggableJava look(programming and feellanguage)|pluggableJava]] portlet [[userDeveloper interface]] [[(software component]]s that are managed and displayed in a [[web portal)|developers]]. A portlet responds to requests from a web client with and generates dynamic content. A portletIt is manageddefined bythrough a '''portlet container'''.various Java Portlet Specification is an example of portlet standards' platform independent [[application programming interface]]s that are intended to enable [[software developer]]s to create portlets that can be [[plug-inRequests (computingJSRs)|plugged into]] any portal supporting the standards.

== DescriptionBackground ==

=== Portlets ===

{{Main|Portlet}}

A ''portlet'' is a [[Pluggable look and feel|pluggable]] [[user interface]] [[software component]] that is 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.

A [[portlet]] is a [[Pluggable look and feel|pluggable]] [[user interface]] [[software component]] that is managed and displayed in a [[web portal]]. A portlet responds to requests from a web client with and generates dynamic content. Some examples of portlet applications are [[e-mail]], [[weather forecasting|weather reports]], [[discussion forum]]s, and [[news]].

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]].

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.

==== Portlet containers ====

A portlet is managed by a ''[[portlet container''.]], A portlet containerwhich 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.

=== Specifications ===

A Java Portlet Specification (JSR) defines a [[design by contract|contract]] between portlets and the portlet container. JSRs provides a convenient programming model for Java portlet developers.

== JSRsSpecifications ==

Portlet standards are 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 Java Portlet Specification (JSR) defines a [[design by contract|contract]] between portlets and the portlet container. JSRs provides a convenient programming model for Java portlet developers.

=== JSR 168 ===

Line 32 ⟶ 27:

==== Portlet Catalog ====

* Initially Java portal vendors had their own portlet development framework thus those portlets were confined to specific portal servers and couldn't be deployed to the rest of the Java portals. After JSR 168 inception, Java portlets may be deployed on any Java portal servers adhering to JSR 168 specifications.

* A Portlets Catalog is a set of portlets that are ready-to-use components for enterprise portals. For those who want to adopt portals certainly need many and variety of portlets to deploy and run. Here Portlets catalog are of use.

Line 40 ⟶ 34:

=== JSR 286 ===

'''JSR-286''' is the Java Portlet specificationSpecification v2.0 as developed under the [[Java Community Process|JCP]] and created in alignment with the updated version 2.0 of [[Web Services for Remote Portlets|WSRP]]. It was released in June 2008.<ref>{{cite web | url = http://www.jcp.org/en/jsr/detail?id=286 | title = JSR 286: Portlet Specification 2.0}}</ref> It was developed to improve on the short-comings of the version 1.0 specification, JSR-168. Some of its major features include:<ref>

{{cite web | last = Hepper | first = Stefan | title = What's new in the Java Portlet Specification V2.0 (JSR 286)? | publisher = IBM | date = 18 March 2008 | url =http://www.ibm.com/developerworks/websphere/library/techarticles/0803_hepper/0803_hepper.html }}</ref>

* Inter-Portlet Communication through events and public render parameters

* Serving dynamically generated resources directly through portlets

Line 49 ⟶ 42:

=== JSR 362 ===

'''JSR-362''' is the Java Portlet specificationSpecification 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 56 ⟶ 49:

* Servlet 3.1 Alignment

* Portlet Hub & XHR IPC

* FacesBridge Integration via JSR 378<ref>[http{{Cite web|url=https://www.jcp.org/en/jsr/detail?id=378|title=The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 378]|website=www.jcp.org}}</ref>

==See also==

Line 66 ⟶ 59:

== External links ==

* [http://www.jcp.org/en/jsr/detail?id=301 JSR 301] (Portlet 1.0 Bridge for JavaServer Faces 1.2 Specification)

* [http://www.jcp.org/en/jsr/detail?id=329 JSR 329] (Portlet 2.0 Bridge for JSF 1.2 Specification)

Line 77 ⟶ 69:

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

[[Category:Web portals]]

[[Category:AMD]]

[[Category:AMD microprocessors]]

[[Category:AMD technologies]]