Note that there are some explanatory texts on larger screens.

plurals
  1. POSAXParseException with XQJ and eXist
    primarykey
    data
    text
    <p>I have a problem with the XQJ API and eXist. Whenever I try to query my files inside the eXist db I get an</p> <pre><code>XQJTO013 - org.xml.sax.SAXParseException; lineNumber: 928; columnNumber: 354; The reference to entity "quotDer" must end with the ';' delimiter. </code></pre> <p>and several other delimiter exceptions throughout the document, whenever <code>&amp;quot;</code> was used ( <code>&amp;amp;</code> doesn´t raise errors btw.).</p> <p>Inside the document however the ";" is set behind the <code>&amp;quot</code>, when I query the file with the eXist GUI Query Dialog it works. When I query the file over the XQJ API inside the baseX db no problem either.</p> <p>I tried to change the SAX Parser from Saxon to Xerces and at last to Oracle the error is raised with each of these.</p> <p>My question is, is there a bug in the XQJ eXist implementation or am I missing something, hope you can help me out. </p> <p>I have the lib of exist-xqj-api-1.0.1 on my classpath.</p> <hr> <p>Here some code for simple reproduction</p> <pre><code>public static void main(String[] args) { XQDataSource xqs = new ExistXQDataSource(); try { xqs.setProperty("serverName", "localhost"); xqs.setProperty("port", "8080"); XQConnection conn = xqs.getConnection("admin", "admin"); XQPreparedExpression xqpe = conn.prepareExpression("element test {'&amp;quot;bla&amp;quot;'}"); XQResultSequence rs = xqpe.executeQuery(); rs.writeSequence(System.out, new Properties()); // SAXParseException is raised here conn.close(); } catch (XQException e) { e.printStackTrace(); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    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.
 

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