Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p><em>Is it correct to say that one can toggle between JSF and CDI scope annotations just by changing the imports in the bean classes without any changes to the Facelets xhtml code?</em></p> </blockquote> <p>Yes.</p> <hr> <blockquote> <p><em>Is it an established pattern that JSF/Facelets should be used only for the xhtml markup code with all scope and lifecycle (plus injection) annotations done using CDI?</em></p> </blockquote> <p>JSF is moving towards CDI. The new <code>@FlowScoped</code> annotation of the upcoming <a href="http://jdevelopment.nl/jsf-22/" rel="nofollow noreferrer">JSF 2.2</a> is evidence of this as this extends from the CDI API. The only disadvantage is that CDI doesn't offer a standard annotation for the tremendously useful JSF <code>@ViewScoped</code> annotation. You'd need <code>@ConversationScoped</code> wherein you manually start and end the conversation, or take a look at a CDI extension like <a href="http://myfaces.apache.org/extensions/cdi/" rel="nofollow noreferrer">MyFaces CODI</a>.</p> <hr> <blockquote> <p><em>In a JBoss AS setting, where is the lifecycle management of the JSF backing beans (using either JSF or CDI annotations) taking place? In the web container or in the EJB3 container?</em></p> </blockquote> <p>The web container (in flavor of a WAR). JSF is built on top of the <a href="https://stackoverflow.com/tags/servlets/info">Servlet API</a>, so it's definitely the web container.</p> <hr> <blockquote> <p><em>In a typical web application given that the SessionScoped beans can be provided by CDI, is there any need for using EJB3 beans other than those of type @Entity, e.g. for the last typical step in each "flow" when information is to be persisted in the database?</em></p> </blockquote> <p>The <code>@Entity</code> is part of JPA, not of EJB. The <code>@Entity</code> is to be used on a model class which is mapped to a database table and usually solely meant to transfer data across the layers. What you're last describing sounds like candidate for a <code>@Stateful</code> EJB. To understand <code>@Stateless</code> vs <code>@Stateful</code> EJBs better, head to this detailed answer: <a href="https://stackoverflow.com/questions/8887140/jsf-request-scoped-bean-keeps-recreating-new-stateful-session-beans-on-every-req/8889612#8889612">JSF request scoped bean keeps recreating new Stateful session beans on every request?</a></p>
    singulars
    1. This table or related slice is empty.
    1. POJSF/Facelets backing beans and EJB3
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJSF/Facelets backing beans and EJB3
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSorry, was beleaguered by the dreaded “Stack Overflow requires external JavaScript from another domain” problem and couldn't promptly accept your answer.
      singulars
      1. PO
      1. USMarcus Junius Brutus
    2. COYour answer is very clear. What I realize is a bit hairy is the relationship between the life-cycle of the EJBs and that of the backing beans. It seems to me that, in principle, EJB beans are a totally different beast and don't have any direct connection to the JSF pages and their backing beans. Yet there seems to be some kind of tenuous dependency and some valid and invalid combos in the life cycles of the respective beans. The article you shared sheds some light but I guess there's no substitute for hands-on experience.
      singulars
      1. PO
      1. USMarcus Junius Brutus
    3. COEJBs should be used as business services. They should not care about any JSF artifacts at all and only deal with model objects (the `@Entity` instances). JSF backing bean (a controller) should in turn have a model object (a `@Entity`) as a property which is been used by the view and also an EJB as a service (injected by `@EJB`). The JSF backing bean should have action methods which will execute the EJB's methods. Those action methods are then bound to command links/buttons/ajaxlisteners in the view.
      singulars
      1. PO
      1. USBalusC
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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