I have written a lot on JSF framework recently, so it’s high time I write one on JSF interview questions and answers. Below is my collection of JSF interview questions with answers. So just go through them before interview and I am sure it will help you out in clearing the JSF interview and land you a job. Note that it’s for JSF 2, not JSF 1.
Domande di Intervista su JSF
- Cos’è JSF?
- Cos’è un Managed Bean?
- Quali sono i tre tipi di tag dei campi di testo forniti da JSF?
- Qual è il significato dell’annotazione @ManagedProperty?
- Cosa indica l’annotazione @ApplicationScoped?
- Cos’è il bundling delle risorse in JSF?
- Spiega l’attributo required e requiredMessage del tag <h:inputText>?
- Quali sono i diversi tipi di navigazione delle pagine supportati in JSF?
- Quali sono le fasi del ciclo di vita di JSF?
- Spiega alcuni degli attributi del tag <h:form>?
- Quali sono i tag dei componenti di comando utilizzati per azione e navigazione?
- Cos’è un componente tabella connesso ai dati?
- Cos’è un evento?
- Come possiamo ottenere l’evento generato?
- Quali sono i diversi tipi di eventi JSF?
- Cos’è una classe di ascolto?
- Qual è l’importanza del tag Facelets?
- Quali sono alcuni dei tag di Facelets?
- Quali sono i diversi tipi di convalida in JSF?
- Quali sono i diversi tipi di espressioni supportate da JSF EL?
- Cosa sono le espressioni di valore immediato e differito?
- Spiega l’espressione di valore e le espressioni di metodo?
- Spiega le annotazioni @ViewScoped, @SessionScoped, @CustomScoped e @RequestScoped?
- Spiega i diversi modi di dichiarare un bean gestito in JSF?
- Qual è l’importanza degli attributi name e eager nel bean gestito?
- Menziona alcuni dei tag del validatore utilizzati in JSF?
- Quali sono i vantaggi dell’utilizzo del framework JSF?
- Quali sono i diversi tag del convertitore JSF?
- Elenca i vantaggi del linguaggio di espressione?
- Cos’è un backing bean?
- Quali sono le librerie di tag JSF standard?
- Menziona alcune delle funzioni che il metodo backing bean esegue?
- Quali sono le diverse implementazioni dell’API JSF?
- Spiega l’architettura di JSF?
- Come vengono renderizzati i diversi componenti nella pagina JSF?
- Il JSF supporta file di configurazione multipli?
- Quali sono le differenze tra un Backing Bean e un Managed Bean?
- Come visualizzare i messaggi di errore in JSF?
- Qual è la significatività del tag selectOne menu in JSF?
- Spiega gli attributi immediate e rendered?
- Indica due modi di binding supportati da JSF?
- Quali sono le configurazioni richieste per il framework JSF?
- Cosa sono le regole di navigazione di JSF?
- Quale è il ruolo dei tag converter di JSF?
- Elenca i vantaggi dei tag della tabella dati in JSF?
- Come implementare l’internazionalizzazione (i18n) in JSF?
- Che cos’è il modello di rendering dei componenti?
- Che cos’è un kit di rendering?
- Che cos’è un oggetto di visualizzazione?
- Cosa intendi per Bean Scope?
- Qual è la differenza tra JSF-1 e JSF-2?
- È possibile avere un’applicazione JSF senza faces-config.xml?
- Quali sono le migliori pratiche per un’applicazione JSF?
- Come si confronta JSF con il framework Spring?
- Perché JSF non è così popolare come il framework MVC Spring MVC, nonostante sia più vecchio?
- È possibile integrare JSF con altri framework popolari come Spring, Hibernate, ecc.?
Domande e risposte per un colloquio su JSF
-
Cos’è JSF?
Java Server Faces (JSF) è una tecnologia per il frontend che semplifica la creazione di componenti dell’interfaccia utente riutilizzando i componenti dell’interfaccia utente. JSF è progettato basandosi sul pattern Model View Controller (MVC) che separa la presentazione, il controller e la logica di business. Per iniziare con JSF, leggi il Tutorial JSF per principianti.
-
Cosa è un Managed Bean?
Un managed bean è una classe Java registrata in JSF che rende possibile l’interazione tra l’interfaccia utente e la logica di business. I managed beans possono essere creati utilizzando l’annotazione @ManagedBean. Per un esempio dettagliato, leggi Esempio di Managed Bean JSF.
-
Quali sono i tre tipi di tag dei campi di testo forniti da JSF?
I tre tipi di tag dei campi di testo sono:
- <h:inputText> – Aggiunge la casella di testo accanto al campo etichetta.
- <h:inputSecret> – Questo tipo viene utilizzato per i campi password in cui i dati inseriti sono nascosti.
- <h:inputTextarea> – Questo tipo di campi viene utilizzato per inserire un grande numero di caratteri.
Per un esempio completo, consulta JSF Text Components.
-
Qual è la significatività dell’annotazione @ManagedProperty?
L’annotazione
@ManagedPropertyci consente di iniettare un managed bean in un altro managed bean. Per capire come funziona, ti preghiamo di leggere Iniezione di Managed Bean in JSF. -
Cosa indica l’annotazione @ApplicationScoped?
The `@ApplicationScoped` annotation indicates that the bean is valid as long as the web application is valid.
The phenomenon of storing the UI labels, date, status messages and other UI textual elements in a separate properties file instead of hardcoding these in a page is called resource bundling. We can use `h:outputLabel` element to pick these values from resource bundle properties file in JSF view pages, for a complete example please refer [JSF Resource Bundle Example](/community/tutorials/jsf-resource-bundle-custom-messages-example-tutorial).
Required attribute indicates that the field is mandatory when set to true. The requiredMessage attribute allows users to specify their own message for the ui components when the fields are mandatory. They are used for declarative validations in JSF view pages, for a complete example please read [JSF Declarative Validation](/community/tutorials/jsf-validation-example-tutorial-validator-tag-custom-validator).
The types of Page navigation supported in JSF are
1. Implicit Navigation
2. Navigation through Managed Bean
3. Navigation through faces-config.xml
4. Forward versus Redirect navigation
5. Conditional Navigation
For detailed explanation, please go through [JSF Navigation Rules](/community/tutorials/jsf-navigation-rule-example-tutorial) and [JSF Action Method Navigation Rule Example](/community/tutorials/jsf-action-method-navigation-example-tutorial-from-action-tag).
There are six lifecycle phases namely;
1. Restore view phase
2. Apply request values phase
3. Process validations phase
4. Update model values phase
5. Invoke application phase
6. Render response phase
For better understanding and detailed explanation of each of life cycle phase, please read [JSF Page Lifycycle Management](/community/tutorials/jsf-page-lifecycle-management).
Some of the important h:form tag attributes are;
- id: This is the unique identifier used to identify a component.
- title: A title for an element of the form used as tooltip.
- onclick: invokes the javascript function to be called when a button is clicked next to an element.
- onsubmit: invokes javascript function to be called on click of form by a submit button.
- onreset: Javascript to be invoked on the reset of the elements in a form.
- ondblclick: Javascript code to be executed when the mouse is double clicked over a field in a form.
- onmouseup: Javascript code to be executed when the mouse button is released over a component.
- onmousedown: Javascript code to be executed when the mouse pointer is clicked down over this element.
- binding: value of the expression linked to a property in a backing bean.
- target: Name of the frame where the resource retrieved is to be displayed.
- accept: the contents list that the form can handle.
- acceptCharSet: defines the list of character encoding that the form will accept.
- style: The CSS style definitions that can be applied for the form
- prependId: flag that indicates whether id should be prepended to the form
- dir: Overrides default text functionality for this component.
To see form component in action, please go through [JSF Form Component Example](/community/tutorials/jsf-form-components-example-tutorial).
The command component tags for performing action and navigation are
1. <h:commandButton> tag - The h:commandButton tag renders a button to submit a form thereby paving a way for processing the data entered by the user.
2. <h:commandLink> tag - The commandLink provides an hyperlink equivalent to anchor tag in HTML that acts like a submit button and can be associated with the backing beans or action class for event handling.
For detailed example, please go through [JSF Command Components Example](/community/tutorials/jsf-command-component-tags-for-action-and-navigation).
The components that are responsible for displaying the relational data in a tabular format are called data bound table components. The <h:dataTable> tag is used for displaying the data components. The <h:column> tag iterates over each record in the data source displayed in rows. Some of the attributes of the h:dataTable tag are;
- bgcolor: background color for the table that is displayed.
- border: width in pixel to be drawn around the table.
- cellpadding: Space between border of each cell and its contents.
- cellspacing: Space between left side of the table and leftmost column and also amount of space between the cells.
- columnClasses: List of css styles separated by comma to be applied to the columns of this table.
- bodyrows: List of row indices separated by comma to be applied for the "tbody" element should be started.
To see dataTable tag in action, please read [JSF dataTable tag](/community/tutorials/jsf-datatable-example).
An event is defined as a signal triggered based upon the user actions such as click of button, hyperlink, changing the input value etc. JSF tells the component to invoke the appropriate listener class that process the event generated by the user.
The generated event can be obtained by calling event.getComponent as
```
UIComponent ui = new UIComponent();
MyFacesEvent ev1 = new MyFacesEvent(ui);
UIComponent sc1 = ev1.getComponent();
```
There are three types of JSF events namely
1. Action Events: Action events are the events that are generated for the ui components like command button or command hyperlink.
2. Value Change Events: Value change events refers to the UI components textfield, radio button, list box etc. The value change event will get fired as soon as the value is changed in the UI component.
3. Phase Events: This type of event involves the events to be fired in one of the six phases of JSF lifecycle either during start or towards the end of each phase.
You can get more details about these events at [JSF Events Example](/community/tutorials/jsf-event-listener-action-phase-value-change).
A class which is associated with an event is called a listener class. For example, if the event is a valueChange event then the corresponding listener class `ValueChangeListener` is associated with it. Read more at [JSF Listeners Example](/community/tutorials/jsf-event-listener-action-phase-value-change) to learn more about these listeners.
JSF provides a special set of tags that gives the flexibility to manage common tags/parts in one place for more than one application. These tags allow us to create a common layout that can be used across applications. You can include facelets tags using below code;
```
<html
xmlns="https://www.w3.org/1999/xhtml"
xmlns:ui="https://java.sun.com/jsf/facelets"
>
```
I have written a very long article for facelets tags, go check it out at [JSF Facelets Tags Example](/community/tutorials/jsf-facelet-tags-example-tutorial).
Some of the important facelets tags are;
- <ui:component> tag
- <ui:composition> tag
- <ui:decorate> tag
- <ui:define> tag
- <ui:fragment> tag
- <ui:include> tag
There are two types of validations namely;
1. **Declarative Validations**: The validations that are fired using JSF standard validators or Bean validators fall under declarative type.
2. **Imperative validation**: The standard validation messages would not be sufficient in all the cases and sometimes may require complex validations that are declared by the user overriding the standard validations and these are called Imperative validations.
Check out complete details of these validation types at [JSF Validation Example](/community/tutorials/jsf-validation-example-tutorial-validator-tag-custom-validator).
JSF Expression Language supports following types of expressions.
1. Immediate value expressions
2. Deferred value expressions
3. Value expression and method expression
Check out complete details about these at [JSF EL Tutorial](/community/tutorials/jsf-expression-language-jsf-el).
Immediate expressions are evaluated and results are rendered as soon as the page is displayed initially. The syntax for immediate evaluation is `${}`. Deferred expressions are evaluated during the lifecycle phase whenever it is requested by the user. The syntax for deferred evaluation is `#{expression}`.
Value expressions usually fetch a value or set a value. These expressions can be further categorized into rvalue and lvalue expressions. lvalue expressions can both read and write data whereas rvalue expressions can only read data. A method expression allows user to invoke a public method of the bean that returns the result necessary for validating the data component and handling events.
**@ViewScoped**: annotation indicates that the bean is alive as long as the user interacts with the same JSF view page in the browser. **@SessionScoped**: annotation indicates that the bean is valid as long as the HTTP session is alive. **@CustomScoped**: annotation indicates that the bean lives as long as the bean's entry in the custom Map which is created for this scope lives. **@RequestScoped**: annotation indicates that the Bean lives as long as the HTTP request-response lives.
1. Use `@ManagedBean` annotation in the java class indicating that the class is a managed bean as;
```
@ManagedBean(name="Greetings", eager="true")
```
If the name attribute is not specified the name is defaulted to the class name as java naming standards. For example class Car will be named "car" and CarDetails will be named "carDetails".
2. Declare the managed bean in faces-config.xml file as;
```
<managed-bean>
<managed-bean-name>Greetings</managed-bean-name>
<managed-bean-class>com.Greetings.Greetings</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
```
**name**: The name attribute indicates the managed bean with the name specified. If the name is not specified then the bean name is same as the class name. **eager**: If eager is set to "true" then managed bean is created before it is requested for the first time and if set to false the bean is created when it is requested.
- f:validateLength: Validates length of a string
- f:validateLongRange: Validates range of numeric value
- f:validateDoubleRange: Validates range of float value
- f:validateRegex: Validate JSF component with a given regular expression
Some of the benefits of using JSF framework are;
- Clean separation between presentation and business logic.
- Manages UI state across multiple server requests.
- Implementation of custom components.
- Easier flow of data between the components.
- JSF specs that helps custom implementations such as PrimeFaces
- f:convertNumber: tag is used to convert a string value to a number of required format.
- f:convertDateTime: tag is used to convert a string value to a date of required format.
- CustomConverter: allows user to define their own convertor in JSF.
- Arithmetic, logical, relational operations can be used in expression language.
- Automatic type conversion.
- Shows missing values as empty strings instead of NullPointerException.
- Provides easy access to predefined objects such as request.
A JavaServer Faces application includes one or more backing beans, each of which is a type of managed bean that can be associated with the components used in a particular page.
1. JSF Core Tags library
2. JSF HTML tags library
Use below namespace configurations to use them in JSF xhtml pages.
```
<html xmlns="https://www.w3.org/1999/xhtml"
xmlns:h="https://java.sun.com/jsf/html"
xmlns:ui="https://java.sun.com/jsf/facelets"
xmlns:c="https://java.sun.com/jsf/core">
```
The html tags can now be used as with the h prefix as <h:head>,<h:form> etc and core tags with c prefix as <c:validateBean>,<c:validator> etc.
- Validating a component’s data
- Handling an event fired by a component
- Performs processing to determine the next page to which the application must navigate
- ADF Faces: Oracle's implementation for the JSF standard.
- Reference Implementation (RI): by Sun Microsystems.
- Apache MyFaces: open source JavaServer Faces (JSF) implementation.
- Primefaces: JSF components with Ajax framework.
JSF is developed based on the Model View Controller(MVC) pattern. The Model VIew Controller separates the business logic from presentation. The JSF application contains
- UI components represented as stateful objects on the server
- Server-side helper classes
- Validators, event handlers, and navigation handlers
- Application configuration resource file for configuring application resources
- JavaBeans components as models containing application-specific functionality and data
- A custom tag library for representing event handlers and validators
- A custom tag library for rendering UI components
Below image shows the JSF applications architecture diagram. [](https://journaldev.nyc3.cdn.digitaloceanspaces.com/2015/03/JSF-Architecture-Diagram.png)
JSF components are rendered in the xhtml pages by the tag libraries included, such as JSF core, html and facelets tag libraries.
Yes, any number of faces configuration files can be used but should be declared in the web.xml file as shown below.
```
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.1" xmlns="https://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://xmlns.jcp.org/xml/ns/javaee
https://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config1.xml,/WEB-INF/faces-config2.xml</param-value>
</context-param>
</web-app>
```
Backing Beans should be defined in request scope whereas managed bean can be defined in request,session or application scopes.Backing bean is referenced by a form whereas a managed bean is registered with JSF and created automatically when needed.
The h:messages tag shows all the error messages at one place corresponding to UI elements. The "for" attribute can be used to represent the field for which error message has to be displayed. For a complete example, please read [JSF Error Messages Example](/community/tutorials/jsf-error-messages-example-tutorial).
The selectOne enables users to select a single value from the list of values. This component can be rendered as a list box, a set of radio buttons or a menu.
The immediate attribute if set to true can force validations, events and conversions processed during request phase of the lifecycle. Command component’s immediate attribute indicates what happens when the component gets activated. If the button’s immediate attribute is set to true and associated text field’s immediate attribute set to false then the event is processed without applying the field’s value to the model. In other words the value entered in the field does not even reach the model when the button is clicked but immediately processed in the above scenario. The rendered attribute indicates whether a component should be rendered or not in the view page. Rendered attribute can use arithmetic operators and literals with rvalue expression but not lvalue expressions.
1. Binding the component’s value to a bean property or other external data source
2. Binding the component’s instance to a bean property
There are two configuration files namely;
1. web.xml: This is the general web application configuration file containing the details of deployment. This contains the faces config file responsible for handling the application.
2. faces-config.xml: allows to configure the application, managed beans, converters, validators, and navigation.
The rules provided by JSF Framework to describe the view to be shown when a button or link is clicked is called a navigation rule. For complete details, please read [JSF Navigation Rules Tutorial](/community/tutorials/jsf-navigation-rule-example-tutorial).
The convertor tags convert the UI component's data to object used in a managed bean and vice versa. For example, these tags can convert a text into date object and can validate the format of input as well.
- DataTable can iterate over collection or array of values to display data.
- DataTable provides attributes to modify its data in easy way
Read more at [JSF Data Table Example](/community/tutorials/jsf-datatable-example).
Internationalization is a mechanism in which status messages, GUI component labels, currency, date are stored outside the source code in resource bundles and retrieved dynamically rather than hardcoding in the program based on the user locale.
The JavaServer Faces component architecture is designed such that the functionality of the components is defined by the component classes, whereas the actualities of the rendering itself can be defined by a separate renderer called as component rendering model.
A render kit defines how component classes map to component tags that are appropriate for a particular client.
A view object is a model object used specifically in the presentation tier but defined outside it. It contains the data that must be displayed in the view layer and the logic to validate user input, handle events, and interact with the business-logic tier.
Bean scope is the mechanism of binding the beans and other objects to be available in the different components of a web application.
- JSF1 does not support the usage of annotations but JSF2 supports annotations that makes it far better than JSF1.
- JSF1 Ajax support was limited, however JSF2 support all the ajax features.
- JSF1 does not provide Template concepts whereas JSF2 does.
- JSF1 was first released and API was having a lot of bugs, JSF2 is totally redesigned and can be used as MVC framework in larger applications.
In JSF 1.0 faces-config.xml is mandatory whereas JSF 2.0 supports annotations which does not need faces-config.xml.
The best practices for JSF application includes
- Avoid using JSF components for static value.
- Short component Id
- Avoid component bindings
- Facelets for dynamic includes
Spring uses Inversion of Control and Dependency Injection whereas JSF does not. Spring has built in modules for Login-Logout available for ready integration whereas in JSF we have to write the login feature manually. Since Spring uses dependency injection the user based pojo classes can be injected with springs whereas JSF is tightly coupled with Java EE architecture.
Some of the reasons I could thought of are;
- There are many implementations of JSF like Mojarra, Primefaces, Richfaces etc which makes it difficult for the user to comprehend learn and adapt to whereas Spring MVC has only one implementation maintained by a Single group of developers which avoids confusion.
- Spring has got great integration with data management through standalone or ORM frameworks out of the box which is lacking in JSF based implementation.
- DI and IOC design patterns makes it very easy to integrate existing legacy applications with new Spring based applications whereas JSF does not have such kind of capabilities.
- JSF is a component based framework whereas Spring is a Request-Response based framework and hence easy to understand and relates closely to MVC, Struts2 and other similar frameworks
Yes, we can integrate JSF framework with Spring, Hibernate, JDBC etc. Since JSF is more focused on view components, we can utilize it for user interface and other frameworks as backend server side integration and ORM tools. Some of the posts you should look for integrations are;
- [JSF and JDBC integration example](/community/tutorials/jsf-database-example-mysql-jdbc)
- [JSF and Spring MVC integration example](/community/tutorials/spring-jsf-integration)
- [JSF, Spring MVC and Hibernate integration example](/community/tutorials/jsf-spring-hibernate-integration-example-tutorial)
- [JSF Authentication Login Logout example](/community/tutorials/jsf-authentication-login-logout-database-example) showing use of HttpSession for session management
Questo è tutto per le domande e risposte dell’intervista su JSF, spero che ti saranno utili per le interviste sulle domande relative a JSF.
Source:
https://www.digitalocean.com/community/tutorials/jsf-interview-questions-and-answers