Community Summary
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.
Portlet 2.0 Bridge for JavaServer Faces 1.2:
Specification:
Reference Implementation:
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 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 read/write to a discussion forum or wiki for my JSR.
http://wiki.apache.org/myfaces/PortletBridge
# 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.