Databases
StackOverflow2013
Postsdbo
POJSP tricks to make templating easier?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJSP tricks to make templating easier?
    primarykey
    data
    text
    <p>At work I've been tasked with turning a bunch of <code>HTML</code> files into a simple <code>JSP</code> project. It's really all static, no serverside logic to program. I should mention I'm completely new to Java. JSP files seem to make it easy to work with common includes and variables, much like <code>PHP</code>, but I'd like to know a simple way to get something like template inheritance (<code>Django</code> style) or at least be able to have a base.jsp file containing the header and the footer, so I can insert content later.</p> <p><em>Ben Lings</em> seems to offer some hope in his answer here: <a href="https://stackoverflow.com/questions/490390/jsp-template-inheritance">JSP template inheritance</a> Can someone explain how to achieve this?</p> <p>Given that I don't have much time I think dynamic routing is a little much, so I'm happy to just to have URLs map directly onto <code>.jsp</code> files, but I'm open to suggestion.</p> <p><em>Thanks.</em></p> <p><strong>edit:</strong> I don't want to use any external libraries, because it would increase the learning curve for myself and others who work on the project, and the company I work for has been contracted to do this.</p> <p><strong>Another edit:</strong> I'm not sure if <code>JSP tags</code> will be useful because my content doesn't really have any template variables. What I need is a way to be able to do this:</p> <p><code>base.html:</code></p> <pre><code>&lt;html&gt;&lt;body&gt; { content.body } &lt;/body&gt;&lt;/html&gt; </code></pre> <p><code>somepage.html</code></p> <pre><code>&lt;wrapper:base.html&gt; &lt;h1&gt;Welcome&lt;/h1&gt; &lt;/wrapper&gt; </code></pre> <p>with the output being:</p> <pre><code>&lt;html&gt;&lt;body&gt; &lt;h1&gt;Welcome&lt;/h1&gt; &lt;/body&gt;&lt;/html&gt; </code></pre> <p>I think this would give me enough versatility to do everything I need. It could be achieved with <code>includes</code> but then I would need a top and a bottom include for each wrapper, which is kind of messy.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USScott
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJSP tricks to make templating easier?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJSP tricks to make templating easier?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJSP tricks to make templating easier?
      1. USJared
      1. VTFavorite
    1. This table or related slice is empty.
 

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