JSF Interview Question

1) Which standard converters have their own tags? DateTimeConverter and NumberConverter are two standard converters that have their own tags convertDateTime and convertNumberrespectively that help configuring the format of the component data by configuring tag attributes. a. DateTimeConverter : A component data can be converted to a Date object using convertDateTime tag within the component tag like,

b. NumberConverter : Converter for dealing with numbers such as type of number, maximum integer digits, currency symbol etc.

2) What are the ways of using standard converters of JSF? Standard converters other than the two which have their own tags (DateTimeConverter and NumberConverter) can be used in one of the following three ways. The first one converts the model value of the component and the other two ways convert the component's local value.

a) Bind UI Component to Backing Bean Property : Make sure that the component has its value bound to a backing bean property of the same type as the converter. For example, converting component data to a float number requires binding the component to the property like :

b) Use “converter” attribute on the UI Component : Using the converter attribute of the component tag. Just specify the fully qualified class name or ID of the converter in the converter attribute. If the component is not bound to a bean property then this option can be used. For example,

c) Use Tag with ConverterId Attribute : Using converter tag within the component tag and refer the converter by specifying the ID of the converter in the convertId attribute. For example:

3) When to create and use custom convertors? The main reasons behind creating our converter are :

a) When we want to convert a component's data to a type other than a standard type

b) When we want to convert the format of the data.

4) What are the steps of creating and using custom converter in our application? Creating and using a custom converter requires the following steps :

Steps to follow :

a) Create a class that implements javax.faces.converter.Converter interface.

b) Import necessary packages and classes.

c) Implement two abstract methods "getAsObject()", "getAsString()" provided by Converter interface. getAsObject() method converts the String (User Input) to Object and getAsString() method converts the Object to String to send back to the page.

d) Register the converter class in configuration file (faces-config.xml) adding element. This element has child elements (name of the converter to be used while programming )and ( name of the converter class which we have created).

e) Create view page where tag is used with attribute "converterId" which specifies the name of the converter which we have specified in element of element in "faces-config.xml" file.

f) Use tag to display the error message.

5) What are the ways to register the custom converters in faces context? After creating custom converter class implementing Converter interface it needs to register in the faces context. This can be done in one of the two ways :

a) Register the converter class with the id. This id is used in tag in our view page (For example, JSP).

b) Use this converter in the view page as :

c) Register the converter class to handle all "Email" objects, for example, automatically.

d) If we register the EmailConverter class to handle all Email objects automatically then there is no need to use the tag in view page. Use this converter as :