Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p><em>My facelet has <code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;</code> at the top.</em></p> </blockquote> <p>This is irrelevant to the problem. This only tells the XML parser which charset to use when reading the XML file content before parsing it into a tree based hierarchy.</p> <p>Your concrete problem can have 2 possible causes:</p> <ol> <li><p>The HTTP request character encoding is not set right. This is however not a normal situation as JSF/Facelets by default already uses UTF-8 throughout all layers. This problem can however occur whenever something else has accessed the HTTP request body before JSF/Facelets has set the proper character encoding. PrimeFaces 3.x is known to do that. See also <a href="https://stackoverflow.com/questions/9634230/typing-chinese-with-primefaces-editor-component/9839362#9839362">Unicode input retrieved via PrimeFaces input components become corrupted</a>. One of the ways to fix this is creating a filter which look like as in <a href="https://stackoverflow.com/questions/10721342/utf-8-form-submit-in-jsf-is-corrupting-data/10721475#10721475">UTF-8 form submit in JSF is corrupting data</a>.</p></li> <li><p>The JDBC connection character encoding is not set right. The MySQL JDBC driver uses the client platform default character encoding instead of the server table character encoding. Make sure that your MySQL JDBC URL look like as follows:</p> <pre class="lang-none prettyprint-override"><code>jdbc:mysql://localhost:3306/db_name?useUnicode=yes&amp;characterEncoding=UTF-8 </code></pre></li> </ol>
    singulars
    1. This table or related slice is empty.
    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. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

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