Databases
StackOverflow2013
Postsdbo
POError creating SAX parser
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError creating SAX parser
    text
    copied!<p>I am using JasperReports and I am hitting an exception when I am trying to generate an html page hosted by my tomcat server.</p> <p>The line:</p> <pre><code>JasperReport jasperReport = JasperCompileManager.compileReport( "C:/Documents and Settings/axc1888/workspace/OATS/WebContent/status.jrxml"); </code></pre> <p>ends up with the exception:</p> <pre><code>net.sf.jasperreports.engine.JRRuntimeException: Error creating SAX parser at net.sf.jasperreports.engine.xml.JRReportSaxParserFactory.createParser(JRReportSaxParserFactory.java:108) at net.sf.jasperreports.engine.xml.JRXmlDigesterFactory.createParser(JRXmlDigesterFactory.java:1338) at net.sf.jasperreports.engine.xml.JRXmlDigesterFactory.createDigester(JRXmlDigesterFactory.java:1313) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:205) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:170) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:154) at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:146) ... Caused by: org.xml.sax.SAXNotRecognizedException: http://java.sun.com/xml/jaxp/properties/schemaLanguage at gnu.xml.aelfred2.XmlReader.getProperty(XmlReader.java:181) at gnu.xml.aelfred2.XmlReader.setProperty(XmlReader.java:166) at gnu.xml.aelfred2.JAXPFactory$JaxpParser.setProperty(JAXPFactory.java:147) at net.sf.jasperreports.engine.xml.JRReportSaxParserFactory.configureParser(JRReportSaxParserFactory.java:139) at net.sf.jasperreports.engine.xml.JRReportSaxParserFactory.createParser(JRReportSaxParserFactory.java:103) ... 8 more </code></pre> <p>I believe it has something to do with server paths...</p> <p>Thanks in advance.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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