Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The Jetty <code>resources</code> folder should not be used for application files. A J2EE web application (war) should be self-contained -- and in Jetty, reside only on the /webapps folder -- and its only binding to the container (Jetty servlet engine) is via the <code>web.xml</code> deployment descriptor.</p> <p>Since property files may be read from the classpath and the Jetty <code>resources</code> folder is part of the system classpath, a property file there could be read by the web application class loader. Note that there are other ways to read property files as well and the Jetty <code>resources</code> folder should not be used for application properties. Also, the application may not be portable as other application servers have different forms of webapp classloader isolation.</p> <p>If the below architecture approach does not work for you, then your only approach would be to expand (explode the war) in the /webapps folder and hope for the best when files are edited.</p> <p>Tackling this from a different angle, - if your web application depends on <code>.properties</code> and <code>.xhtml</code> files in order to function properly, then these files are probably not 'content'. The fact that there is a business process that requires them to to be updated <em>ad hoc</em> does not make them content. - 'content' is something like text, images, and videos that is added, edited and removed by an administrative user. The application does not depend on it for correct execution, it merely reads and passes it on the browser.</p> <p>Suggestions:</p> <ol> <li>I would suggest that you deploy your application every time there is a change to the <code>.xhtml</code> or <code>.properties</code> files change. If the editors of these files are power business users, you might think of a git push-pull tool for them and a continuous build hook, so that when they make changes and push them to the git repository, the application gets tagged with a newer version and gets built and deployed. If there is a problem (tag not closed in xhtml), then it would be easy to roll back to the last tag.</li> <li>Alternately, if the changes are minor (such as text descriptions), then modify the application to read them from an arbitrary external file (outside the webapp) -- a location that is provided to the webapp on startup. You can then package a 'default' version of the file in the webapp, but the code would attempt to look in the specified external location first.</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POExternalizing static content from a WAR and serve both on jetty
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAkber Choudhry
    1. USAkber Choudhry
    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. This table or related slice is empty.
    1. COWhat are the cons of having `.xhtml` and `.properties` files as external modifiable files outside of the WAR package? 1. will not be possible in the project environment setup. With 2. you suggest that I should make another configuration/properties file, but I do not understand the benefit of this approach.
      singulars
      1. PO
      1. USqtips
    2. COI have added 2 paragraphs in the beginning to elaborate further. The rule is : if your application breaks because of a malformed or corrupted xhtml or properties file -- then it is code and not content, and should go through a release cycle. If you want to treat text as content (good!) then keep it outside the webapp and write code to read it in on loading, while providing a default version within the app so that it does not break.
      singulars
      1. PO
      1. USAkber Choudhry
 

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