JSFG

JSFG0100I: Liberty initialized JSF integrations for JSF provider {0} on application {1}.
JSFG0101E: No JSF implementations were found in application {0}. A JSF implementation that contains one of the following javax.faces.application.ApplicationFactory implementations must be available to the application {1}.
JSFG0102E: Liberty is unable to obtain the application name from the JSF application {0} by using JNDI.
JSFG0103E: The JSF specification API version available to application {0} is {2}, but it needs to be within the version range {1}. 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.
JSFG0104E: The JSF implementation version available to application {0} is {2}, but it needs to be within the version range {1}. 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.
JSFG0851W: Sun RI 1.2 JSF Implementation is detected for webapp {0} but a MyFaces StartupServletContextListener is also registered.
JSFG0852W: The Sun RI 1.2 JSF Implementation is detected but was not able to be initialized. JSF might not have initialized properly for webapp {0}.
JSFG0853W: The MyFaces JSF Implementation is selected for {0} but a Sun RI ConfigureListener is also registered.
JSFG0854W: The WebSphere MyFaces JSF Implementation is detected but was not able to be initialized for webapp {0}.
JSFG0855W: Exception caught while attempting to register the JSF lifecycle listener {0}. JSF might not have initialized properly for webapp {1}.