Explanation | Liberty JSF integrations are initialized for the indicated application, which allows CDI and JSF integrations to function. |
Action | Informational message. No user action needed. |
Explanation | Liberty JSF integrations are only supported for a specific set of third-party JSF implementations. One of the listed ApplicationFactory implementations must be available to the indicated application. |
Action | Include either the Apache MyFaces or the Mojarra JSF implementation inside of the indicated application. Alternatively, if you would like to use the default JSF implementation that is provided by Liberty, Apache MyFaces, use the jsf-2.2 feature instead of jsfContainer-2.2. |
Explanation | Registration of an application with the Liberty JSF Container requires the application name to be available by performing a JNDI lookup of "java:app/AppName". |
Action | Verify that the jndi-1.0 feature is enabled and ensure that performing a JNDI lookup, such as InitialContext.doLookup("java:app/AppName"), works from within the application. |
Explanation | The version of jsfContainer that is enabled must correspond to the same JSF API version packaged within the indicated application. |
Action | Ensure that the JSF API that is packaged within the indicated application corresponds to the version of jsfContainer that is enabled. Liberty determines the version of the JSF API by checking the Specification-Version manifest attribute of the .jar file that contains a JSF API class. |
Explanation | The version of jsfContainer that is enabled must correspond to the same JSF implementation version packaged within the indicated application. |
Action | Ensure that the JSF implementation that is packaged within the indicated application corresponds to the version of jsfContainer that is enabled. Liberty determines the version of the JSF implementation by checking the Specification-Version manifest attribute of the .jar file that contains the MyFaces or Mojarra ApplicationFactory class. |
Explanation | A listener was found that does not match the JSF implementation that is in use. |
Action | Remove the StartupServletContextListener or use the corresponding JSF implementation. |
Explanation | The JSF implementation might not have properly initialized. |
Action | Examine the log files to determine the cause of the failure. |
Explanation | A SunRI ConfigureListener was found that does not match the JSF implementation in use. |
Action | Remove the ConfigureListener or use the corresponding JSF implementation. |
Explanation | The JSF implementation might not have properly initialized. |
Action | Examine the log files to determine the cause of the failure. |
Explanation | An exception occurs when registering the listener. |
Action | Examine the log files to determine the cause of the exception. |