First, the definition of JSF
JavaServer Faces (JSF) is a standard framework for building Java web applications
It simplifies development by providing a component-centric approach to developing Java Web user interfaces.
JavaServer Faces was officially proposed in March 2004, version 1.0, which clearly divided the developers of web applications into three roles: web designers, application designers, and UI component developers. From a usage point of view, web designers and application designers can develop programs in a way they are familiar with without invading each other's scope of work, while UI component developers can develop individual components independently, leaving the details to the for them to deal with.
JSF also ensures higher maintainability of applications by integrating the well-built Model-View-Controller (MVC) design pattern into its architecture
Main components:
To represent UI components and manage their state, manipulate events, server-side validation and data transformations; define page navigation; support internationalization and accessibility; provide an extensible API for all features for representing UI components in JSP and Two JSP custom tag libraries that send components to server-side objects.
Technical benefits:
Component-based and event-driven development patterns were introduced, allowing developers to develop web applications in a manner similar to dealing with traditional interfaces. Provides a clear separation of behavior and expression. No special scripting language or markup language is used to connect UI components to the web layer. The JSF technology API is layered directly on top of the Servlet API. Technology provides a rich architecture for managing component state, processing component data, validating user input, and manipulating events.
JSF realizes the following three dreams based on the web
1. Java programmers do not need to worry about the details of HTTP, they can design the background system according to the familiar event-driven model, and combine the background system with the foreground interface through a data transfer interface that can guarantee the correct data type.
2. Web artists without programming knowledge can also use the components provided by the programmer to lay out the look and feel of the user interface.
3. Manufacturers can develop better and more consistent front-end development tools.
Second, the architecture of JSF:
One of the main strengths of JSF is that it is both a user interface standard for Java Web applications and a framework that strictly follows the Model-View-Controller (MVC) design pattern. The clean separation of user interface code (views) from application data and logic (models) makes JSF applications easier to manage. To prepare the JSF context that provides the page's access to application data and to prevent unauthorized or incorrect access to the page, all user interaction with the application is handled by a front-end FacesServlet (the controller).
For more JSF learning, see: https://blog.csdn.net/qjyong/article/details/1833457
