When you develop a Web application using JSF, you can use various JSF functionalities such as defining access to the page view, page re-use, changing or validating types of input values from the client, and controlling events in the application.

You use the ManagedBean or the Expression Language functionality to implement most of the functionalities of JSF.

ManagedBean is a JavaBean that defines methods and the data to be used in the JSP and Facelets pages. For details on ManagedBean, see the JSF specifications.

The Expression Language functionality associates properties and methods defined in the ManagedBean with attributes of the JSF tags by coding properties and methods in a prescribed format. The Expression Language functionality is a part of the JSP specifications. For details, see the JSF specifications.

The following table describes functionalities of the Bean Validation that can be used from JSF.

Table 3-2 Functionalities of Bean Validation that can be used from JSF

You can use the functionalities of the Bean Validation by specifying annotations. The following table describes annotation classes that can be specified for using the functionalities of the Bean Validation. The table also describes the types of variables that can be specified as well as the operations performed when an invalid type of variable is specified.

Table 3-3 Annotation classes and variable types that can be specified in the Bean Validation

Legend:

--: Not Applicable.

JSF operations in Application Server are as follows:

• If you use the Expression Language to specify methods that function as ValueChangeListener, ActionListener, AjaxBehaviorListener, and ComponentSystemEventListener, and if both, a method with arguments and a method without arguments exist with the same name, the method with arguments is invoked.
• If multiple components are present in the f:facet tag, the component coded first is processed in a JSP page, whereas in a Facelets page, all the coded components are processed.
• If the f:subview tag is coded outside the f:view tag, in JSP pages, the value of the f:view is overwritten with the value of f:subview. In Facelets pages, the value of f:view does not change and f:view and f:subview are displayed together.
• You must code the h:head tag when using the f:ajax tag. f:ajax does not function unless the h:head tag is coded.
• When using the valueChangeListener attribute or the f:valueChangeListener tag for processing an event, if you specify ValueExpression in the value attribute of the h:inputText tag and RequestScoped in the scope attribute, the valueChangeListener method is executed even if you do not change the input value.
• If the user application registers a Cookie called csfcfc and sends repeated requests to the Facelets by using the Flash object, an error occurs while reading the data of the Flash object and exception (NullPointerException) handling is done.
• The retry count of the ui:repeat tag will be the value specified in the size attribute + 1.
• Attributes of some tags might become invalid due to the browser specifications. We therefore recommend that you check the browser specifications.
• To enable the required attribute of tags such as composite:attribute, composite:facet, composite:insertFacet, and composite:renderFacet tags, set the value of the context parameter javax.faces.PROJECT_STAGE to Development.
• The value you specify in the context parameter javax.faces.FACELETS_REFRESH_PERIOD serves as the time from receiving the latest request by the Facelets page until the Facelets file update is confirmed.
• Therefore, in an environment where many requests are sent in a short period of time, the time until the confirmation of the update is extended according to the latest request, and there is a possibility that a state continues where the Facelets file is not updated.
• The Bean Validation functionality is usually enabled in Application Server. For details on how to disable the Bean Validation functionality, see10.5.1 Procedure of using Bean Validation from JSF in the uCosminexus Application Server Common Container Functionality Guide.
• Specify the attribute as the target for specifying a value in the f:attribute tag, in which the character string (having java.lang.String type) is treated as the specified value.
• Note that the parameter count of the requests included in the POST data from the client window of the JSF application differs depending on the type of the JSP tag to be used and the usage method. When you want to set a maximum value of the request parameters count in the webserver.connector.limit.max_parameter_count key, we recommend that you validate by using the real JSF application on the same environment as the real environment.
• When the resources of META-INF/resources within the JAR file of the application are updated, the message KDJE39556-W is output at the time of reload. If you access the resource from a JSF when the message is output, you can acquire the updated resources.