-
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
-
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>com.sun.faces.config.ConfigureListener</listener-class> </listener> <listener> <listener-class>com.liferay.faces.bridge.servlet.BridgeSessionListener</listener-class> </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.
- duplicates
-
FACES-1483 Explicitly specify Mojarra ConfigureListener and Liferay Faces BridgeSessionListener in WEB-IN/web.xml descriptor of demo and issue portlets
-
- Closed
-
- is related to
-
FACES-1470 Memory leak for RequestScoped, SessionScoped, and ViewScoped managed-beans when running under Mojarra + JBoss AS
-
- Closed
-
- relates
-
FACES-1595 NoClassDefFoundError regarding JSTL when jsf2-jsp-portlet is deployed on WebLogic
-
- Closed
-
-
FACES-1634 Warning in GlassFish console log: Unable to determine Mojarra InjectionProvider
-
- Closed
-
-
FACES-1656 Provide ability to discover Mojarra InjectionProvider during execution of the JSF lifecycle
-
- Closed
-