JSFG

JSFG0001E: Unable to locate internal dtd: {0}

Explanation	The DTD required to validate faces-config.xml files cannot be located
Action	The ws-jsf.jar file may be corrupted

JSFG0002E: Unable to find write method {0} for bean class of type {1}

Explanation	The bean class does not contain a usable write (set) method
Action	Add a write (set) method to the bean class

JSFG0003E: Unable to invoke write method {0} for bean class of type {1}

Explanation	The write (set) method of the bean could not be successfully executed
Action	Checks the logs for stack traces and other information

JSFG0004E: Unable to access write method {0} for bean class of type {1}

Explanation	The write (set) method of the bean could not be successfully accessed
Action	Check that the method provided is publicly defined

JSFG0006E: Unable to set property since bean and/or property are null. bean: {0} property: {1}

Explanation	The provided bean instance or property is null.
Action	Check your application code to verify that they are setup correctly

JSFG0007E: Unable to find property descriptor {0} for bean class of type {1}

Explanation	The property descriptor for the bean cannot retrieved
Action	Make sure that the bean is correctly defined.

JSFG0008E: Unable to invoke read method {0} for bean class of type {1}

Explanation	The read (get) method of the bean could not be successfully executed
Action	Checks the logs for stack traces and other information

JSFG0009E: Unable to access read method {0} for bean class of type {1}

Explanation	The read (get) method of the bean could not be successfully accessed
Action	Check that the method provided is publicly defined

JSFG0010E: Unable to create property descriptor {0} for bean class of type {1}

Explanation	The provided bean cannot be introspected correctly
Action	Check all the bean method names to verify that they conform to the JavaBeans specification

JSFG0011E: Unable to set property {0} for bean class of type {1} (Value)

Explanation	The bean could not set the value for the specified property.
Action	Check all of the bean property names and types to verify that they are specified properly and conform to the JavaBeans specification.

JSFG0012E: Unable to set property {0} for bean class of type {1} (Array or List)

Explanation	The bean could not set the Array or List for the specified property.
Action	Check all of the bean property names and types to verify that they are specified properly and conform to the JavaBeans specification.

JSFG0013E: Unable to set property {0} for bean class of type {1} (Map)

Explanation	The bean could not set the Map for the specified property.
Action	Check all of the bean property names and types to verify that they are specified properly and conform to the JavaBeans specification.

JSFG0014E: Unable to initialize configuration

Explanation	The faces configuration could not be parsed correctly
Action	The ws-jsf.jar file may be corrupted

JSFG0015E: Unable to find application {0}

Explanation	Unable to find the deployment object matching the application target
Action	Check the application target and try again

JSFG0016E: Unable to find cell

Explanation	Unable to find the cell object
Action	The configuration may be corrupted

JSFG0017E: Invalid implementation name

Explanation	The implementation name passed is not valid
Action	Choose either SunRI1.2 or MyFaces1.2

JSFG0018E: Unable to open archive {0}

Explanation	The archive with the given name could not be opened
Action	Examine the exception to see what may be wrong with the archive

JSFG0019E: You are attempting to use the Flash scope but it is disabled.

Explanation	The Flash scope cannot be used because it is disabled.
Action	Change the setting on the org.apache.myfaces.FLASH_SCOPE_DISABLED context parameter to false if you need to use the Flash scope.

JSFG0100I: Liberty initialized JSF integrations for JSF provider {0} on application {1}.

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.

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}.

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.

JSFG0102E: Liberty is unable to obtain the application name from the JSF application {0} by using JNDI.

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.

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.

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.

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.

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.

JSFG0851W: Sun RI 1.2 JSF Implementation is detected for webapp {0} but a MyFaces StartupServletContextListener is also registered.

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.

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}.

Explanation	The JSF implementation might not have properly initialized.
Action	Examine the log files to determine the cause of the failure.

JSFG0853W: The MyFaces JSF Implementation is selected for {0} but a Sun RI ConfigureListener is also registered.

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.

JSFG0854W: The WebSphere MyFaces JSF Implementation is detected but was not able to be initialized for webapp {0}.

Explanation	The JSF implementation might not have properly initialized.
Action	Examine the log files to determine the cause of the failure.

JSFG0855W: Exception caught while attempting to register the JSF lifecycle listener {0}. JSF might not have initialized properly for webapp {1}.

Explanation	An exception occurs when registering the listener.
Action	Examine the log files to determine the cause of the exception.