Support Managed-Bean: Normally session or application scope.JSF controller-beans typically have JSF action methods (and not actionListener methods). The purpose of a controller bean is to execute some kind of business logic and return a navigation outcome to the JSF navigation-handler. This type of managed-bean participates in the "Controller" concern of the MVC design pattern. Controller Managed-Bean: Normally request scope.JSF backing-beans may also have JSF actionListener and valueChangeListener methods. Although it typically has JavaBean-style properties with associated getters/setters, these are properties of the View - not of the underlying application data model. The purpose of a backing-bean is to support UI logic, and has a 1::1 relationship with a JSF view, or a JSF form in a Facelet composition. This type of managed-bean participates in the "View" concern of the MVC design pattern. Backing Managed-Bean: Normally request scope.The most common use case for a model bean is to be a database entity, or to simply represent a set of rows from the result set of a database query. A JSF model-bean should be a POJO that follows the JavaBean design pattern with getters/setters encapsulating properties. When you see the word "model" - think DATA. This type of managed-bean participates in the "Model" concern of the MVC design pattern. Model Managed-Bean: Normally session scope.Here is a description of the different bean types, as defined in the above article by Neil Griffin: You might want to check this out: making distinctions between different kinds of JSF managed beans.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |