JSR #329 Portlet 2.0 Bridge for JavaServerTM Faces 1.2 Specification
Community Summary
The materials on this page are provided by the Maintenance Lead of this JSR
for evaluation and feedback.
These materials are not final, and are subject to change
as the JSR progresses through the process.
Timeline and Status:
(Updated 11/10/2010)
This is the sister JSR to JSR 301:
JSR 301: Portlet 1.0 Bridge for JavaServer Faces 1.2: describes bridge function and behavior when running on a portlet 1.0 container.
JSR 329: Portlet 2.0 Bridge for JavaServer Faces 1.2: describes bridge function and behavior when running on a portlet 2.0 container.
We originally intended to produce both of these specifications within JSR 301. However, because these specifications are on a different timeline the JCP indicated they needed to be separated into distinct JSRs.
Because work on both of these specifications started in the JSR 301 Expert Group and the interests remain aligned, JSR 329 is largely being used as a repository for the Portlet 2.0 Bridge specification to satisfy JCP requirements. I.e. A duplicate JSR 329 Expert Group, etc, hasn't been established. Rather, the JSR 301 Expert Group continues to discuss and work on both specifications. However, all public postings and status related to the Portlet 2.0 Bridge is now being managed on the corresponding JSR 329 pages.
Portlet 2.0 Bridge for JavaServer Faces 1.2:
Specification:
Current draft available to the public is the Public Review Draft. It can be downloaded from the JSR's homepage". The license for Final Release will be the standard spec license.
Reference Implementation:
The reference
implementation is being developed in the Apache Open Source community.
All interested parties are encouraged to use and/or work on
this implementation. The work is being developed in the PortletBridge
project in Apache MyFaces. Though the project
exists under the MyFaces umbrella, the reference implementation doesn't
require the use of the MyFaces Faces implementation. It will
run with the Faces reference implementation and should run with any
other conforming Faces 1.2 implementation. The decision to
host within Apache MyFaces was largely made so it would be colocated
with the variety of the Faces extension projects (renderkits, etc) that
its important the bridge can run alongside with.
The current binary release is MyFaces Portlet Bridge 2.0.0-alpha2. This version was built in August, 2009 and corresponds to the the Early Draft 2 specification. Problems should be reported via the Apache JIRA system. There is a beta version pending public posting which corresponds to Public Review Draft.
The main trunk to the source for this project is here. This contains any changes that have occurred since publishing the Early Draft 2.
The Final Release of the RI will be licensed using the Apache 2 license.
TCK:
The TCK work is in progress. The Final Release TCK will be licensed using the Apache 2 license.
Current Projected Timeline:
Posting Proposed Final Draft revision: November 2010
TCK complete: November 2010
Standard submitted for JCP approval (assuming no significant changes from the Public Review): November 2010
Transparency checklist
# The public can read who is on the Expert Group.
JSR home page
# The Expert Group business is regularly reported on a publicly readable alias. JSR 329 discussion board
# The schedule for the JSR is publicly available, it's current, and I update it regularly.
Here on the Update tab.
# The public can write to an alias with feedback and comments on my JSR. JSR 329 discussion board
# There is an issue-tracker for my JSR that the public can read.
Apache Jira system.
# I have spoken at conferences and events about my JSR recently.
Nope, JavaOne consistently turns me down.
# I am using open-source processes for the development of the RI and/or TCK.
Yes, for RI (Apache MyFaces PortletBridge) -- kind of for the TCK -- tests are being developed in the same project -- but the test harness isn't.
