Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I understand that your question basically boils down to <em>How can I include Facelets views in a JAR?</em></p> <p>You can do this by placing a custom <a href="http://download.oracle.com/javaee/6/api/javax/faces/view/facelets/ResourceResolver.html" rel="nofollow noreferrer"><code>ResourceResolver</code></a> in the JAR.</p> <pre class="lang-java prettyprint-override"><code>public class FaceletsResourceResolver extends ResourceResolver { private ResourceResolver parent; private String basePath; public FaceletsResourceResolver(ResourceResolver parent) { this.parent = parent; this.basePath = "/META-INF/resources"; // TODO: Make configureable? } @Override public URL resolveUrl(String path) { URL url = parent.resolveUrl(path); // Resolves from WAR. if (url == null) { url = getClass().getResource(basePath + path); // Resolves from JAR. } return url; } } </code></pre> <p>Configure this in webapp's <code>web.xml</code> as follows:</p> <pre class="lang-xml prettyprint-override"><code>&lt;context-param&gt; &lt;param-name&gt;javax.faces.FACELETS_RESOURCE_RESOLVER&lt;/param-name&gt; &lt;param-value&gt;com.example.FaceletsResourceResolver&lt;/param-value&gt; &lt;/context-param&gt; </code></pre> <p>Imagine that you've a <code>/META-INF/resources/foo/bar.xhtml</code> in <code>random.jar</code>, then you can just include it the usual way</p> <pre class="lang-xml prettyprint-override"><code>&lt;ui:include src="/foo/bar.xhtml" /&gt; </code></pre> <p>or even dynamically</p> <pre class="lang-xml prettyprint-override"><code>&lt;ui:include src="#{bean.path}" /&gt; </code></pre> <p>Note: since Servlet 3.0 and newer JBoss/JSF 2.0 versions, the whole <code>ResourceResolver</code> approach is not necessary if you keep the files in <code>/META-INF/resources</code> folder. The above <code>ResourceResolver</code> is only mandatory in Servlet 2.5 or older JBoss/JSF versions because they've bugs in <code>META-INF</code> resource resolving.</p> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/3531432/packaging-facelets-pages-in-a-jar">Packaging Facelets files (templates, includes, composites) in a JAR</a></li> <li><a href="https://stackoverflow.com/questions/9290482/jsf-facelets-template-packaging">JSF facelets template packaging</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to create a modular JSF 2.0 application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to create a modular JSF 2.0 application?
      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. VTUpMod
    1. COThis is exactly what I was after. Knew there had to be a simple way to do this, I just didn't know how. Thank you very much!
      singulars
      1. PO
      1. USSplinterReality
    2. COYou're welcome.
      singulars
      1. PO
      1. USBalusC
    3. COTested, and this does indeed create the solution I was wanting. My final solution will likely be quite nuanced compared with this, but I put the resolver in the .war file, and will simply specify that views go in folder X in the module .jar file as part of the interface contract. This keeps the programming concerns of the modules and application separated better, and allows me to resolve specific resources based on the module they originate in (Only the application knows this with certainty) to avoid namespace collision concerns.
      singulars
      1. PO
      1. USSplinterReality
 

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