Press Room  |  Get Java Here  | 

Printed: Apr 19, 2026
From: http://www.jcp.org/en/jsr/detail?id=286

Standard Format

Specification Leads
	Martin Nicklous	IBM
Expert Group
	Adobe Systems Inc. : Ed Solovey	Adobe Systems Inc. : James Ward	BEA Systems : Subbu Allamaraju
	BEA Systems : Kevin Frender	Butler, Rob : Rob Butler	Dabke, Padmanabh : Padmanabh Dabke
	Day Software, Inc. : Carsten Ziegeler	Dettborn, Torsten : Torsten Dettborn	DeWolf, David H. : David H. DeWolf
	Craig Doremus	Douma, Ate : Ate Douma	eXo Platform SAS : Benjamin Mestrallet
	eXo Platform SAS : Julien Viet	Frid, Slava : Slava Frid	Goenka, Vishal : Vishal Goenka
	IBM : Martin Nicklous	Liferay, Inc : Jorge Ferrer	Mann, Kito D.
	Millidge, Stephen : Stephen Millidge	Novell, Inc. : Martin Holzner	Novotny, Jason : Jason Novotny
	Oracle : Michael Freedman	Pandey, Punit : Punit Pandey	Red Hat : Thomas Heute
	Red Hat : Julien Viet	SAP SE : Ilya Rybak	Severance, Charles : Charles Severance
	Suleiman, Hani : Hani Suleiman	Sun Microsystems, Inc. : Wesley Budziwojski	Sun Microsystems, Inc. : Deepak Gothe
	SunGard Higher Education : Bruce Martin, Ph.D	TIBCO Software Inc. : Danny Machak	Vignette : Siddharth Chaudhary
	Ziegeler, Carsten : Carsten Ziegeler
Contributors

Updates to the Original JSR

The following information has been updated from the original proposal.

2015.07.14:
In Maintenance, the JSR moved to JCP 2.9. It was completed in JCP version 2.6.

2009.02.06:

Maintenance Lead: Martin Scott Nicklous

E-Mail Address: scott.nicklous@de.ibm.com

Telephone Number: +49-7031-16-4808

Fax Number: +49-7031-16-3335

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: IBM

Name of Contact Person: Stefan Hepper

E-Mail Address: sthepper@de.ibm.com

Telephone Number: +49 7031 16 3445

Fax Number: +49 7031 16 4888

Specification Lead: Stefan Hepper

E-Mail Address: sthepper@de.ibm.com

Telephone Number: +49 7031 16 3445

Fax Number: +49 7031 16 4888

Initial Expert Group Membership:

Supporting this JSR:

BEA
IBM
Oracle
SAP
Sun Microsystems
Vignette

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR requests the creation of the next version of the Portlet Specification. The main goal of this version is to align the Java Portlet Specification with J2EE 1.4, other JSRs relevant for portlet programming, like JSR 188, the next version of Web Services for Remote Portlets (WSRP)

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

A Java^TM extension for the J2EE platform.

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

A Java^TM extension for the J2EE platform.

2.4 Should this JSR be voted on by both Executive Committees?

No

2.5 What need of the Java community will be addressed by the proposed specification?

The new Portlet Specifications will add functionality that was not addressed in the first version specification, other JSRs were not final at the time JSR 168 went to public review (e.g. J2EE 1.4 and JSR 188), or because additional research was needed before determining the correct approach.

The requirement areas we intend to address include, but are not limited to, the following:

- Corrections and clarifications
- Add access to CC/PP data via JSR188 API
- Introduction of portlet filters
- Inter-portlet communication as defined in WSRP 2.0
- Public render parameters as defined in WSRP 2.0
- J2EE 1.4 support
- Enhance caching support and align caching with WSRP
- Enhance the portlet tag library
- Align with WSRP versions 2.0
- Coordinate with the JSF EG to better align JSF with portlets

The final list of features included in this JSR will be determined by the Expert Group.

2.6 Why isn't this need met by existing specifications?

These areas were not addressed in the first version of the Portlet Specification.

2.7 Please give a short description of the underlying technology or technologies:

Version 2.0 of the Portlet Specification will be based on the version 1.0 that was defined in the JSR 168. Version 2.0 will be binary compatible with Version 1.0.

2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

javax.portlet.

2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No

2.10 Are there any security issues that cannot be addressed by the current security model?

No

2.11 Are there any internationalization or localization issues?

No

2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

No

2.13 Please describe the anticipated schedule for the development of this specification.

To be determined by the expert group, initial target is to have a working EG by December 2005, a early public draft beginning of 2006, a public draft by mid 2006 and a final version by end of 2006.

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.

We anticipate a mixture of mailing list and occasional face to face or teleconference meetings.

2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.

The EG will consist of all major players of the Java-based portal market and will be open to ISVs and tool vendors. We will provide early public drafts in order to get public feedback as early as possible.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

The RI will be implemented inside the open source project Pluto at Apache.

RI and TCK will be stand-alone versions based on J2EE 1.4.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).

Not applicable

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

The specification, RI, and TCK will be freely available for independent implementations.

If this specification, or a future version of this specification, is included in a future version of a Java platform specification, this specification will remain available for use outside the platform specification, and will continue to be evolved outside the platform specification.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

Portlet Specification, Version 1.0
http://jcp.org/en/jsr/detail?id=168

Java 2 Platform Enterprise Edition, Version 1.4
http://java.sun.com/j2ee/docs.html

Java Server Pages, Version 2.0
http://jcp.org/en/jsr/detail?id=152

Java Servlet Specification, Version 2.4
http://jcp.org/en/jsr/detail?id=154

CC/PP Processing
http://jcp.org/en/jsr/detail?id=188

Web Services for Remote Portlets, Version 2.0 (in progress)
http://www.oasis-open.org

3.2 Explanation of how these items might be used as a starting point for the work.

As an incremental upgrade to the technology, we will be building on the last revision, version 1.0 of the Portlet Specification. The other mentioned materials will be taken into account to create a version 2.0 of the Portlet Specification that complies with these mentioned standards.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

Contact Us

© 2026, Oracle Corporation and/or its affiliates. Terms of Use. Privacy Policy. Trademarks