Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Table that sets a <code>book</code> request scope variable:</p> <pre><code>&lt;h:dataTable value="#{homePage.books}" var="book" styleClass="homeTable" rowClasses="evenColumn,oddColumn"&gt; </code></pre> <p>Managed bean that sets a <code>book</code> session scope variable:</p> <pre><code>&lt;managed-bean&gt; &lt;managed-bean-name&gt;book&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;omitted.for.anonymity.beans.Book&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;session&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; </code></pre> <p>Just guessing, but I wonder if the Expression Language is resolving the session bean here for some reason. It shouldn't - the <a href="http://java.sun.com/javaee/5/docs/api/javax/servlet/jsp/el/ScopedAttributeELResolver.html" rel="nofollow noreferrer">ScopedAttributeELResolver</a> <em>"searches the page, request, session and application scopes for an attribute with the given name and returns it, or null if no attribute exists with the current name."</em> But it isn't beyond possibility that there is a bug in the Expression Language implementation. Try changing the name of the <code>var</code> attribute to avoid collision or resolve it explicitly to the scope using <code>#{requestScope.book.title}</code>.</p> <pre><code>&lt;!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd"&gt; </code></pre> <p>I notice from your doctype that you're using JSF 1.1. I recommend upgrading to at least 1.2 (preferably 2.0) if you can.</p>
    singulars
    1. This table or related slice is empty.
    1. POJSF not displaying first row, first column data
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMcDowell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJSF not displaying first row, first column data
      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 the man. I added that line, but it only moved the problem to the author column. Additionally adding the same fix to the author column fixed everything. You hypothesized that there may be a "bug" in the EL - care to elaborate on what the prefix of requestScope "does" and why you thought this would fix it? Up vote and check marked as correct answer - will also look into upgrading JSF implementation. I know there were lots of dependencies to chase down, (had to match up with a specific jsp spec and stuff like that).
      singulars
      1. PO
      1. USRuss
    2. COThe JSP spec defines a strict ordering of how variables are resolved. Implicit variables (like requestScope and sessionScope) are always resolved first. Using this prefix means EL won't hunt through the scopes to resolve your object. See your version of the JSP spec for the defined order and list of implicit variables (probably JSR 245 or JSR 152).
      singulars
      1. PO
      1. USMcDowell
 

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