Blogs

News

Announcement: Liferay Faces 3.1.2-ga3 Released

Neil Griffin

June 03, 2013

A Minute Read

On June 1, 2013 Liferay released the 3^rd General Availability (GA) release of Liferay Faces:

Liferay Faces 3.1.2-ga3 (JSF 2.1 + Liferay 6.1.x)
Liferay Faces 3.0.2-ga3 (JSF 2.1 + Liferay 6.0.x)
Liferay Faces 3.0.2-legacy-ga3 (JSF 2.1 + Liferay 5.2.x)
Liferay Faces 2.1.2-ga3 (JSF 1.2 + Liferay 6.1.x)

Project Links

Version Scheme

Please refer to the Liferay Faces Version Scheme wiki article for a detailed explanation of the version numbering.

Release Highlights

This is a maintenance release that has 50+ bug fixes, 20+ improvements, and 10+ new features. For full details, please refer to the Release Notes.

New Feature: CDI Support

One of the exciting new features in this release is support for Contexts and Dependency Injection (CDI), thanks to the new Liferay CDI Portlet Bridge. We developed a new jsf2-cdi-portlet demo that shows how to use annotations like javax.inject.Inject, javax.inject.Named, and javax.enterprise.context.RequestScoped. For more information, refer to the new Developing JSF Portlets with CDI wiki article.

Critical Bug Fixes

[FACES-224] JSF 2.x f:viewParam feature not working due to RenderRequestPhaseListener stopping lifecycle phase execution after RESTORE_VIEW phase
[FACES-257] Bridge generates URLs that can be incompatible with Liferay friendly URLs
[FACES-1463] References to BridgeRequestScope instances causing memory leak

[FACES-1470] Memory leak for RequestScoped, SessionScoped, and ViewScoped managed-beans when running under Mojarra + JBoss AS
[FACES-1496] Memory leak with Mojarra and JSF2 resources
[FACES-1591] ViewExpiredException when Ajax is used on WebLogic

Testing

We have strengthened our commitment to quality with a new suite of automated integration tests that utilize Selenium via Arquillian. The tests exercise the Liferay Faces demo portlets and also verify bug fixes with issue tester portlets. For example, the FACES-257 Selenium Test exercises the FACES-257-portlet in order to verify that f:viewParam is working in conjuntion with Liferay friendly URLs.