Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to put the webcontent files in a <code>/faces</code> root folder, exactly the path as it is in the URL.</p> <p>Another way is to replace the <code>url-pattern</code> of <code>/faces/*</code> by <code>*.jsf</code> so that you can invoke them without the <code>/faces</code> path, for example: <code>http://localhost:8080/Monaco/cadastro/pessoa/listar.jsf</code>. By the way, you do <strong>not</strong> need to rename the actual <code>.jsp</code> files to <code>.jsf</code>.</p> <p>If you want to prevent direct access to the JSP files (otherwise one would be able to request the <code>.jsp</code> file and face a <code>RuntimeException: FacesContext not found</code>), then you can best move the files (including folder structure) into the <code>WEB-INF</code> folder.</p> <p>Hope this helps.</p> <p><strong>Edit:</strong> you added the appserver logs. The root cause of the first problem is the following:</p> <pre><code>java.lang.ClassNotFoundException: org.apache.commons.digester.Digester </code></pre> <p>This is fairly self-explaining: the mentioned class is missing in the runtime classpath. As the package name already hints it is Apache Commons Digester which you can get at <a href="http://commons.apache.org/digester" rel="nofollow noreferrer">http://commons.apache.org/digester</a>. Put it in the runtime classpath (<code>WEB-INF/lib</code>) and restart. See if the subsequent errors will disapear or not (may be indirectly caused by the same problem). If not, come back and edit the stacktrace in your question (don't forget to select it and press the code button (0101011010) or press the <kbd>Ctrl</kbd>+<kbd>K</kbd>).</p>
    singulars
    1. This table or related slice is empty.
    1. POJSF + RichFaces gives me an HTTP Status 404 in my pages
      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. POJSF + RichFaces gives me an HTTP Status 404 in my pages
      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. COThankz for the reply! Yeah... I was using the /faces/ pattern in the urls and itwas not working (it was, but before I install the RichFaces jars), tried the changes you said, changed /faces/* to *.jsf and tried to access the url http://localhost:8080/Monaco/cadastro/pessoa/listar.jsf, still not work...
      singulars
      1. PO
      1. USAlaor
    2. COWell, maybe `FacesServlet` failed to start. Read the appserver logs.
      singulars
      1. PO
      1. USBalusC
    3. COIn the logs I have a lot of erros related to org.jboss.beans.metadata.plugins.AbstractPropertyMetaData, only this class, can it be the root of all evils? I think it's the combo of JRE and JBoss version, because I had a look in a friends code and it's almost the same thing, and it's working, but in an older version of JBoss... Let's see...
      singulars
      1. PO
      1. USAlaor
 

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