Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In a Servlet, you can get request scoped beans by:</p> <pre><code>Bean bean = (Bean) request.getAttribute("beanName"); </code></pre> <p>and session scoped beans by:</p> <pre><code>Bean bean = (Bean) request.getSession().getAttribute("beanName"); </code></pre> <p>and application scoped beans by:</p> <pre><code>Bean bean = (Bean) getServletContext().getAttribute("beanName"); </code></pre> <hr> <p>If you're running in a dependency injection capable framework/container and the bean is managed by CDI's <a href="http://docs.oracle.com/javaee/6/api/javax/inject/Named.html" rel="noreferrer"><code>@Named</code></a> instead of JSF's <a href="http://docs.oracle.com/javaee/6/api/javax/faces/bean/ManagedBean.html" rel="noreferrer"><code>@ManagedBean</code></a>, it's even more easy:</p> <pre><code>@Inject private Bean bean; </code></pre> <hr> <p>Regardless of the scope, when you're <em>actually</em> inside the <a href="http://docs.oracle.com/javaee/6/api/javax/faces/context/FacesContext.html" rel="noreferrer"><code>FacesContext</code></a> (i.e. the current HTTP request has been served through the <a href="http://docs.oracle.com/javaee/6/api/javax/faces/webapp/FacesServlet.html" rel="noreferrer"><code>FacesServlet</code></a>), then the normal JSF2 way is using <a href="http://docs.oracle.com/javaee/6/api/javax/faces/application/Application.html#evaluateExpressionGet%28javax.faces.context.FacesContext,%20java.lang.String,%20java.lang.Class%29" rel="noreferrer"><code>Application#evaluateExpressionGet()</code></a>:</p> <pre><code>FacesContext context = FacesContext.getCurrentInstance(); Bean bean = context.getApplication().evaluateExpressionGet(context, "#{beanName}", Bean.class); </code></pre> <p>which can be convenienced as follows:</p> <pre><code>@SuppressWarnings("unchecked") public static &lt;T&gt; T findBean(String beanName) { FacesContext context = FacesContext.getCurrentInstance(); return (T) context.getApplication().evaluateExpressionGet(context, "#{" + beanName + "}", Object.class); } </code></pre> <p>and can be used as follows:</p> <pre><code>Bean bean = findBean("bean"); </code></pre> <hr> <p>However, when you're already inside a <a href="http://docs.oracle.com/javaee/6/api/javax/faces/bean/ManagedBean.html" rel="noreferrer"><code>@ManagedBean</code></a>, then using <a href="http://docs.oracle.com/javaee/6/api/javax/faces/bean/ManagedProperty.html" rel="noreferrer"><code>@ManagedProperty</code></a> is cleaner since it's more declarative.</p> <pre><code>@ManagedProperty("#{bean}") private Bean bean; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POGet JSF managed bean by name in any Servlet related class
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBalusC
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGet JSF managed bean by name in any Servlet related class
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COYou're second suggestion about just injecting the bean was so amazingly simple I had totally overlooked it. As always, your response is perfectly to the point. Thanks so much for your work here on SO.
      singulars
      1. PO
      1. USjnt30
 

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