Remove lifecycle implementation from bridge in favor of declaratively registering phase-listeners via faces-config.xml

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: liferay-faces-2.1.1-ga2, liferay-faces-3.0.1-legacy-ga2, liferay-faces-3.0.1-ga2, liferay-faces-3.1.1-ga2
• Fix Version/s: liferay-faces-2.1.2-ga3, liferay-faces-3.0.2-legacy-ga3, liferay-faces-3.0.2-ga3, liferay-faces-3.1.2-ga3
• Component/s: Liferay Faces Bridge Impl / Demos / Tests
• Labels: None

The original design of Liferay Faces Bridge was to have a different JSF lifecycle implementation for each phase of the portlet lifecycle. Each lifecycle implementation would register phase-listeners that were appropriate, so as to avoid having phase-listeners run un-necessarily. Although this was a more performant design, the Bridge TCK expected that only one lifecycle would exist. Because of this, FACES-1371 was implemented in order to consolidate all of the different lifecycle implementations into a single one with id "javax.faces.lifecycle.LifecycleFactory.DEFAULT".

Upon review of this design, it became apparent that the lifecycle implementation could be removed entirely in favor of declaratively registering phase-listeners via faces-config.xml.