Improve and enhance JSF1.2 <-> JSF2.0 compatibility layer

• 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

In order to minimize JSF differences between branches, Liferay Faces Bridge has a variety of *Compat.java classes that isolate such differences.

But there are some classes that dont have compatibility layers, which makes backports full of painful merge conflicts:

The main culprit is BridgeConfigImpl – the monolithic design of the class makes it very difficult to backport. For example, JSF 1.2 has a view-handler-factory, but JSF 2.0 does not. JSF 2.0 has a bridge-flash-factory, but JSF 1.2 and JSF 2.2 do not.

There are other classes including ApplicationImpl, BeanManagerImpl, and BridgeSessionListener that also lack a compatibility layer.

So this task involves the refactoring some existing classes and developing additional compatibility classes in order to facilitate easier backports.