Java Portlet Specification: Difference between revisions

Revision as of 06:23, 10 May 2016

Latest revision as of 14:18, 21 March 2024

(40 intermediate revisions by 26 users not shown)

Line 1:

{{Short description|Technical standard}}

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.

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

TheA '''Java Portlet Specification''' defines a [[design by contract|contract]] between the [[portlet containerPortlet|portlets]] and their [[portletPortlet container|containers]]s; andthey provides a convenient [[programming model]] for [[Java (programming language)|Java]] portlet [[Developer (software)|developers]]. It is defined through various Java Specification Requests (JSRs).

== JSR 168Background ==

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

==== Portlet containers ====

A portlet is managed by a [[portlet container]], which runs [[portlet]]s and provides them with the required runtime environment. A portlet container receives requests from the portal to execute requests on the portlets hosted by it.

== Specifications ==

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 ===

The Java Portlet Specification V1.0 was developed under the [[Java Community Process]] as Java Specification Request '''JSR 168''', and released in its final form in October 2003.<ref>{{cite web|url=http://www.jcp.org/en/jsr/detail?id=168|title=JSR 168|publisher=JCP}}</ref>

The Java Portlet Specification V1.0 introduces the basic portlet programming model with:

* two phases of action processing and rendering in order to support the [[Model-View-Controllermodel–view–controller|Model–View–Controller]] pattern.

* portlet modes, enabling the portal to advise the portlet what task it should perform and what content it should generate

* window states, indicating the amount of portal page space that will be assigned to the content generated by the portlet

Line 13 ⟶ 26:

* Portal development as a way to integrate the different web-based applications for supporting deliveries of information and services.

==== JSRPortlet 286Catalog ====

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

* A JSR 168 portlets catalog makes sure that portlets under this catalog may run on any standards–compliant Java portal server. Types of portlet solution (vertical domains and technology) like collaboration, social networking, community, content management, utility, calendaring, HRM all are available in these catalogs.

* 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's easy to keep a single set of solution and deploy it on many.

=== 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 onof the version 1.0 of the 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

* Serving [[AJAX]] or [[JSON]] data directly through portlets

* Introduction of portlet filters and listeners

=== PortalJSR server362 ===

'''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>

{{See also|List of enterprise portal vendors}}

{{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

* Explicit Render State

* CDI 1.2 Integration

* Servlet 3.1 Alignment

* Portlet Hub & XHR IPC

* FacesBridge Integration via JSR 378<ref>{{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==

{{See* also|[[List of enterprise portal vendors}}]]

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

* [[JSR 168 Portlet Catalog]]

== References ==

{{Reflist}}

{{unreferenced|article|date=November 2014}}

== External links ==

* [http://www.jcp.org/en/jsr/detail?id=286301 JSR 286301] (versionPortlet 21.0 ofBridge thefor JavaJavaServer portletFaces 1.2 specificationSpecification)

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

* [http://www.jcp.org/en/jsr/detail?id=286 JSR 286] (version 2.0 of the Java portlet specification)

* [http://portals.apache.org/pluto/ JSR 168 Open Source Reference Implementation at Apache]

* [https://web.archive.org/web/20060110193512/http://community.java.net/portlet/ Open source JSR 168/WSRP community] at http://java.net

* [http://research.nesc.ac.uk/rapid/ Rapid Portlet Generator] for generating JSR 168-compliant portlets

* [http://soap-portlet.sourceforge.net/ Dynamic SOAP Portlet], for dynamic integration of [[SOAP]] services in JSR-168 portals

{{standard-stubWeb interfaces}}

[[Category:Java enterprise platform|Portlet specification]]

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

[[Category:Web portals]]

[[Category:AMD]]

[[Category:AMD microprocessors]]

[[Category:AMD technologies]]