Note that there are some explanatory texts on larger screens.

plurals
  1. POJSF/Facelets backing beans and EJB3
    primarykey
    data
    text
    <p>I have a few questions on the various options and best practices when using JSF with EJB3.1. The mental model I have, given the daunting amount of choices and combinations available, is far from clear so some questions may not make sense.</p> <p>JSF/Facelets reference backing beans (I am using the term "<em>backing bean</em>" for beans whose properties are written or read from Facelets pages) through EL code that is agnostic as to the actual annotations used in the bean classes (javax.faces.bean.* or javax.enterprise.context.*).</p> <p>Is it correct to say that one can toggle between <strong>JSF</strong> and <strong>CDI</strong> scope annotations just by changing the imports in the bean classes without any changes to the Facelets <em>xhtml</em> code?</p> <p>Is it an established pattern that JSF/Facelets should be used only for the <em>xhtml</em> markup code with all scope and lifecycle (plus injection) annotations done using <em>CDI</em>?</p> <p>In a <strong>JBoss AS</strong> setting, where is the lifecycle management of the JSF backing beans (using either <strong>JSF</strong> or <strong>CDI</strong> annotations) taking place? In the web container or in the EJB3 container?</p> <p>In a typical web application given that the <strong>SessionScoped</strong> beans can be provided by CDI, is there any need for using EJB3 beans other than those of type <strong>@Entity</strong>, e.g. for the last typical step in each "flow" when information is to be persisted in the database?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload