Warning in console log during JSF portlet deployment: Unable to determine Mojarra InjectionProvider

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 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

If the warning "Unable to determine Mojarra InjectionProvider" appears in the in console log during portlet deployment, then the following should be added to the portlet's WEB-INF/web.xml deployment descriptor:

<!-- Guarantee order of startup listeners (JSF implementation must be specified before the bridge). -->
<listener>
	<listener-class&gt;com.sun.faces.config.ConfigureListener</listener-class&gt;
</listener>
<listener>
	<listener-class&gt;com.liferay.faces.bridge.servlet.BridgeSessionListener</listener-class&gt;
</listener>

In order to make sure that Liferay Faces Bridge is able to determine/discover the Mojarra InjectionProvider, the Mojarra ConfigureListener must be explicitly specified in the WEB-INF/web.xml descriptor before the BridgeSessionListener.

If deploying portlets with JBoss AS, it is an absolute necessity to explicitly specify listener order (as well as upgrading to Mojarra 2.1.20+) in order to fix memory leaks described in FACES-1470.

If using a different application server or servlet container, then it is still recommended to explicitly specify listener order in order.