+ Javaserver Faces (jsf) Interview Questions and Answers, Question1: What is JSF (or JavaServer Faces)? Question2: What are the advantages of JSF?. JSF interview questions: JSF (Java Server Faces) is a Posted in Interview Questions, tag libraries. Download JSF Interview Questions PDF. Articles Tutorials Interview Questions & Answers Certifications Free Books JavaServer Faces Interview Questions What is JSF (or JavaServer Faces)? JavaServer Faces (JSF) is an industry standard and a framework for building.
|Language:||English, Spanish, French|
|ePub File Size:||15.74 MB|
|PDF File Size:||20.16 MB|
|Distribution:||Free* [*Regsitration Required]|
Java Server Faces or JSF: It is a java based web application framework to Top 14 JSF Interview Questions & Answers . Download PDF. Top 14 JSF Interview Questions & Answers. 1) Explain what is JSF or Java Server Faces? Java Server Faces or JSF: It is a java based web application. 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.
What Is Managed Bean? Developers can also create their own components based on these APIs, and many third parties have already done so and have made their component libraries publicly available. We promise not to spam you. Spring FAQs. In a nutshell, Faces has the following advantages over Struts:.
When the other requests are made, then the other actions are performed. The execution phase is further divided into various sub-phases which are as follows: Restore view phase Apply request value phase Process validation phase Update model values phase Invoke application phase Render response phase Various actions which are performed are- applying of request parameter values, conversions, and validations of component values, updating managed beans, etc.
What are the features of Facelets used in JSF? Some of the features of Facelets in JSF are listed below: XHTML is used for the creation of web pages. It supports tag libraries. It also supports expression language. Templating is used for components and pages. Tell about the life cycle of Java Server Faces. For simple applications, the life cycle phases are automatically managed by the Java Server Faces application framework.
Not only it is managed automatically, but it also allows you to manage the lifecycle phases manually.
The initial stage in the life cycle of a Java Server Faces application is when the client requests for a page through HTTP and ends when the server responds the request. The life cycle phase of a JSF application is divided into phases: Execute phase Render phase.
What are the various features of Java Server Faces?
Some of the main features of Java Server Faces are listed below: Inbuilt components are provided in it. The implementation of the latest Facelet technology has made it the most used interface for building the web applications. The expression language, which represents a union of expression languages provided by JSF, is an important feature.
A rich set of inbuilt tools and libraries are provided with the help of which web applications can be developed easily and rapidly.
List the available scopes for managed bean in JSF. Following is a list of some scopes for a managed bean class: It helps in interacting with a web application.
View ViewScoped — when a user is interacting with a single page of any web application, then this scope comes into play. None NoneScoped — it indicates that no scope is defined for that particular application. Custom CustomScoped — it is a user-defined scope which is also nonstandard. List some advantages of Facelets. Following are some of the advantages of Facelets: Functional extensibility of components and other server-side objects are provided through customization.
Compilation time is much faster. The expression language is validated at compile time. Rendering can be done with a high performance. What do you understand by managed bean in JSF?
It is a pure java class which is a collection of the set of properties and getter-setter methods. It can also work as a model for the java server faces framework. This can be used by two methods: Configuration into XML file Using annotations. Subscribe Our NewsLetter.
Subscribe Now. Join Onlineinterviewquestions. In JavaServer Faces technology, user interfaces can be created easily with its built-in UI component library, which handles most of the complexities of user interface management. Offers a clean separation between behavior and presentation.
Provides a rich architecture for managing component state, processing component data, validating user input, and handling events.
Robust event handling mechanism. Events easily tied to server-side code. Render kit support for different clients Component-level control over statefulness Highly 'pluggable' - components, view handler, etc JSF also supports internationalization and accessibility Offers multiple, standardized vendor implementations. What are differences between struts and JSF? In a nutshell, Faces has the following advantages over Struts:. Because Struts is a web application framework, it has a more sophisticated controller architecture than does JavaServer Faces technology.
It is more sophisticated partly because the application developer can access the controller by creating an Action object that can integrate with the controller, whereas JavaServer Faces technology does not allow access to the controller. In addition, the Struts controller can do things like access control on each Action based on user roles. This functionality is not provided by JavaServer Faces technology.
Struts includes a powerful layout management framework, called Tiles, which allows you to create templates that you can reuse across multiple pages, thus enabling you to establish an overall look-and-feel for an application. The Struts validation framework includes a larger set of standard validators, which automatically generate both server-side and client-side validation code based on a set of rules in a configuration file.
You can also create custom validators and easily include them in your application by adding definitions of them in your configuration file. A standard component API for specifying the state and behavior of a wide range of components, including simple components, such as input fields, and more complex components, such as scrollable data tables.
Developers can also create their own components based on these APIs, and many third parties have already done so and have made their component libraries publicly available. A separate rendering model that defines how to render the components in various ways.
For example, a component used for selecting an item from a list can be rendered as a menu or a set of radio buttons. An event and listener model that defines how to handle events generated by activating a component, such as what to do when a user clicks a button.
Conversion and validation models for converting and validating component data. What are the available implementations of JavaServer Faces? The main implementations of JavaServer Faces are: What typical JSF application consists of? A typical JSF application consists of the following parts: JavaBeans components for managing application state and behavior.
Event-driven development via listeners as in traditional GUI development. JavaServer Faces applications are just like any other Java web application. They run in a servlet container, and they typically contain the following: JavaBeans components containing application-specific functionality and data. Event listeners. Pages, such as JSP pages. Server-side helper classes, such as database access beans. In addition to these items, a JavaServer Faces application also has: A custom tag library for rendering UI components on a page.
A custom tag library for representing event handlers, validators, and other actions. UI components represented as stateful objects on the server.
Backing beans, which define properties and functions for UI components. Validators, converters, event listeners, and event handlers. An application configuration resource file for configuring application resources.
JavaBean objects managed by a JSF implementation are called managed beans. A managed bean describes how a bean is created and managed.
It has nothing to do with the bean's functionalities. Backing beans are JavaBeans components associated with UI components used in a page. Backing-bean management separates the definition of UI component objects from objects that perform application-specific processing and hold data. The backing bean defines properties and handling-logics associated with the UI components used on the page.
Each backing-bean property is bound to either a component instance or its value. A backing bean also defines a set of methods that perform functions for the component, such as validating the component's data, handling events that the component fires and performing processing associated with navigation when the component activates. What are the differences between a Backing Bean and Managed Bean?
There is nothing special in a Backing Bean that makes it different from any other managed bean apart from its usage.