Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This,</p> <pre><code>import javax.faces.view.ViewScoped; </code></pre> <p>is the <a href="http://docs.oracle.com/javaee/7/api/javax/faces/view/ViewScoped.html" rel="noreferrer">JSF 2.2-introduced CDI-specific</a> annotation, intented to be used in combination with CDI-specific bean management annotation <code>@Named</code>. </p> <p>However, you're using the JSF-specific bean management annotation <code>@ManagedBean</code>. </p> <pre><code>import javax.faces.bean.ManagedBean; </code></pre> <p>You should then be using any of the scopes provided by the very same <a href="http://docs.oracle.com/javaee/7/api/javax/faces/bean/package-summary.html" rel="noreferrer"><code>javax.faces.bean</code> package</a> instead. The right <a href="http://docs.oracle.com/javaee/7/api/javax/faces/bean/ViewScoped.html" rel="noreferrer"><code>@ViewScoped</code></a> is over there:</p> <pre><code>import javax.faces.bean.ManagedBean; import javax.faces.bean.ViewScoped; @ManagedBean @ViewScoped public class MenusBean implements Serializable{ </code></pre> <p>If you use the wrong combination, the bean behaves as a <code>@RequestScoped</code> bean and be recreated on each call.</p> <p>Alternatively, if your environment supports CDI (GlassFish/JBoss/TomEE with Weld, OpenWebBeans, etc), then you could also replace <code>@ManagedBean</code> by <code>@Named</code>:</p> <pre><code>import javax.inject.Named; import javax.faces.view.ViewScoped; @Named @ViewScoped public class MenusBean implements Serializable{ </code></pre> <p>It's recommended to move to CDI. The JSF-specific bean management annotations are candidate for deprecation in future JSF / Java EE versions as everything is slowly moving/unifying towards CDI.</p>
    singulars
    1. This table or related slice is empty.
    1. PO@ViewScoped bean recreated on every postback request when using JSF 2.2
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBalusC
    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.
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COok awsome, this solves the problem, but only partially :( , after changing the annotation and load the page, it works fine, but when I go to the "reports" menu it starts with creating again and again, and when I go back to "live monitoring" menu it creates one more and stops. any ideas ?
      singulars
      1. PO
      1. USRima
    2. COWell, this is awkward. Is the bean now managed by JSF or CDI? Have you tried the other? Are you absolutely positive that rebuild/redeploy is successful and that browser cache is clean and crisp? (Ctrl+Shift+N in Chrome).
      singulars
      1. PO
      1. USBalusC
    3. COI honestly don't know what a CDI is, but I don't have a package javax.inject, so I suppose it's managed by JSF (sorry total noob here). [here](http://speedy.sh/zEdjF/primefaces-test-3.zip) is my project ; I cleared the cache in FF and tried with eclipse built-in browser, they both give the same result.
      singulars
      1. PO
      1. USRima
 

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