【正文】 系統(tǒng)中的應(yīng)用 [J] .電子工業(yè)大學(xué) ,20214,8790 [4] 何明 編著 .從實(shí)踐中學(xué)習(xí) Oracle/SQL[M].北京：清華大學(xué)出版社 . [5] 宣小平編著． ASP數(shù)據(jù)庫(kù)系統(tǒng)開發(fā)實(shí)例導(dǎo)航 [M]．北京：人民郵電出版社 [6] 李剛編著 .輕量級(jí) Java EE企業(yè)應(yīng)用實(shí)戰(zhàn)： Struts 2+Spring[M].電子工業(yè)大學(xué)出版社 . [7] 張陽(yáng) .基 .于 JSF框架 Web應(yīng)用開發(fā)的研究 [J].計(jì)算機(jī)與數(shù)字工程 . [8] 劉海婷著 .基于 JSF框架的信息管理系統(tǒng)的設(shè)計(jì)和實(shí)現(xiàn) [J].計(jì)算機(jī)工程設(shè)計(jì) ,2021,20~22 [9] 李峰 ,周寧 編著新一代 web應(yīng)用框架 JSF[J].計(jì)算機(jī)科學(xué) ,2021,1518 [10] 鄧睿 編著 .基于 JSF、 Spring和 Hibernate的技術(shù)資料綜合管理系統(tǒng)設(shè)計(jì) [J].計(jì)算機(jī)應(yīng)用與軟件 .2021 [11] Yang Qiyong， Yang Jinsong， Yao Rongjiang, et al. Comprehensive Evaluation of Soil Fertility by GIS and Improved Grey Relation Model[J].Transactions of the CSAE,2021,78(9). 陳浜：基于 jsf 的網(wǎng)絡(luò)營(yíng)銷系統(tǒng)的設(shè)計(jì) 22 附錄 附錄 A 引用的外籍文獻(xiàn)及譯文 Life cycle of JSF Restore view, the Apply Request Values。 event processing, processing inspection。 handling events, the update model values。 event calling application processing。 processing event table according to each stage possible execution order and event processing arrangement, but the JSF life cycle is not fixed. You can change the order of execution, skip certain stages, or pletely separate from the life cycle. For example, if an invalid request value is copied to the ponent, it will re present the current view, and may not perform some stages. You can also choose to pletely break away from the JSF, such as handling a delegate to a servlet or another application framework. In this case can perform a method call that will redirect the user to another page or web resources, and then use the request scheduler (from the facescontext request object obtained) is forwarded to the appropriate web resources. You can also call to re display the original view. The most important is that in the use of life cycle to anize your development work at the same time will not be bound by its. You can modify the default life cycle when you need to, without having to worry about breaking the application. In most cases, you will find that the life cycle of the JSF is worthwhile, because it is very logical. The form must be checked before executing any application logic, and the field data must be converted before executing the test. If you insist on using the life cycle, you can focus on the details of the test and conversion, and do not have to pay attention to the stage of the request process itself. Also note that other Web frameworks have similar life cycles。 but not so obvious. Some developers who use JSF may never have written ponents or extended frameworks, and other developers have focused on these tasks. Although the JSF life cycle is the same for almost any project, developers can participate in different stages of their role in the project. If you are primarily engaged in the overall application development, it is possible to focus on several phases of the request processing life cycle: In the first phase of the JSF life cycle, a request is made by servlet FacesServlet in the view of recovery. The servlet checks the request and extracts the view ID (the view ID is determined by the name of the JSP page). JSF frame controller uses this view ID to find the ponents for the current view. If the view does not exist, the JSF controller create it, then call the get method returns a null), then call set (at this time background Bing ponents will is assign values), and then into the rendering stage. If the view already exists, the JSF controller uses it, and then calls the ponent corresponding to the set method to restore the view (which will pass the value of the last time), and the get method does not call the. View contains all GUI ponents. This phase of the life cycle has three views: the new view, the initial view, and the postback, each of which is different. For the new view, JSF builds a view of the Faces page, and connects the event handler function to the ponent. The view is saved in a FacesContext object. JacesContext storage status information, JSF need to use this information for the current request to manage the status of the GUI ponent. FacesContext stores the view in its viewRoot property。 viewRoot contains all the JSF ponents that correspond to the current view ID. For the initial view (the first load page), JSF creates an empty view. Fill this empty view when you are dealing with the JSP page. After filling the initial view, JSF directly into the display response phase. For postback, a page that has been returned to a previous visit, the view that corresponds to the page already exists, so just restore it. In this case, the JSF uses the state information of the existing view to re construct its state. The goal of applying the requested value phase is to obtain the current state of each ponent. First, you have to get or create a ponent from the FacesContext object, and then get the value of the object. Component values are often retrieved from the request parameters, but can also be retrieved from the cookie or request header. For many ponents, the value of the request parameter is stored in the submittedValue of the ponent. If the direct event processing property of the ponent is true, the value is converted to the correct type and is checked (further in the next phase). Then, the converted value is stored in the ponent. If the value conversion or value test fails, then an error message is generated and placed in the FacesContext, which displays the response phase, and the error message is displayed with any other test error. Conversion and inspection usually occur during the process of testing. Component to convert and store its submittedValue. For example, if the field is bound to a Integer property, then the value is converted to a Integer. If the value conversion fails, an error message is generated and placed in the FacesContext. The error message is displayed in the display response phase, along with any other test error. In the event of the first event of the life cycle