Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You will get this error when you're using JSP as view technology and you're using <code>#{...}</code> in template text such as (the <code>&lt;p&gt;</code> is just examplary, it can be any plain HTML element):</p> <pre><code>&lt;p&gt;#{bean.property}&lt;/p&gt; </code></pre> <p>It's namely not supported in JSP, but it is supported in its successor Facelets. In JSP, you would need to explicitly use <code>&lt;h:outputText&gt;</code>:</p> <pre><code>&lt;p&gt;&lt;h:outputText value="#{bean.property}"&gt;&lt;/p&gt; </code></pre> <p>However, in your particular code snippet wherein you're using <code>#{...}</code> in a JSF component already, that can only happen if the <code>a4j</code> tag library is not properly been registered as a JSP tag library by <code>&lt;%@ taglib %&gt;</code>, or if the <code>a4j</code> tag library cannot be found in the classpath. This way the <code>&lt;a4j:ajax&gt;</code> tag is not parsed and thus treated as plain text, including all attributes with EL expressions. So the <code>#{question.setParameters}</code> is treated as EL in template text, which is not supported in JSP.</p> <p>But your problem is bigger: the RichFaces 4.x component library, which the <code>&lt;a4j:ajax&gt;</code> is part of, <strong>does not support JSP</strong>. JSP is deprecated since JSF 2.0 and succeeded by Facelets. All JSF component libraries such as RichFaces have decided to drop support for JSP, because it's a hell of a lot of work to develop and support tag libraries and components for the two different view technologies JSP and Facelets. So even if you have RichFaces 4.x already in the classpath and you've properly registered it by <code>&lt;%@ taglib %&gt;</code>, it would never work in JSP, simply because the JSP <code>.tld</code> file does not exist for the <code>a4j</code> namespace.</p> <p>In order to use JSF 2.0 compatible component libraries, you've to migrate from JSP to Facelets. An alternative is to use the older RichFaces 3.x version instead. Version 3.3.3 supports JSF 2.0 on JSP. It offers the <code>&lt;a4j:support&gt;</code> tag to achieve the same. But keep in mind that you're going backwards in technology this way. You should keep moving forwards. Drop JSP and go for its successor Facelets.</p> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/4441713/migrating-from-jsf-1-2-to-jsf-2-0">Migrating from JSF 1.2 to JSF 2.0</a></li> <li><a href="https://stackoverflow.com/tags/facelets/info">Our Facelets wiki page</a> - contains several tutorial links at the bottom</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. PO#{...} is not allowed in template text
      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. This table or related slice is empty.
    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. 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