Content deleted Content added
c/e lead and sections; removed dead or potentially spamming external links and those used as references |
|||
Line 1:
{{Short description|Technical standard}}
{{more citations needed|date=January 2013}}
== Description ==
'''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 ===
▲A ''
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 containers ====
A
===
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>
Line 24 ⟶ 31:
* Portal development as a way to integrate the different web-based applications for supporting deliveries of information and services.
==== 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.▼
▲* 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.▼
▲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 ===
'''JSR-286''' is the Java Portlet specification 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>
Line 45 ⟶ 48:
* Introduction of portlet filters and listeners
=== 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>
Line 54 ⟶ 56:
* Servlet 3.1 Alignment
* Portlet Hub & XHR IPC
* FacesBridge Integration via JSR 378<ref>[http://www.jcp.org/en/jsr/detail?id=378 JSR 378]</ref>
==See also==
* [[List of enterprise portal vendors]]
* [[Web Services for Remote Portlets]] (WSRP)
== References ==
Line 67:
== External links ==
* [http://www.jcp.org/en/jsr/detail?id=
* [http://www.jcp.org/en/jsr/detail?id=329 JSR 329] (Portlet 2.0 Bridge for JSF 1.2 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
{{Web interfaces}}
| |||