Error (Parser does not support specificatoin null version null) while generating a jasper report

Jaspersoft Community 'Read-Only' as of July 8, 2022

Transition to New TIBCO Community Just Weeks Away

You can still search, review wiki content, and review discussions in read-only mode. Please email with questions or issues requiring TIBCO review or response.

We have a JAVA Application (Oracle ADF) that runs under Weblogic server version

This application contains reporting functionality where dynamic reports are being constructed and generated in PDF using jasper report.


We are not using JASPER SERVER deployed on weblogic.
Inside the app we have included the jasper report client jar (JasperReports® Library CE - latest version v6.19.1) inside it.


The application works well in Weblogic 12.1.3 .

On the other hand, we are migrating to Weblogic we started getting the below error whenever we try to generate a jasper report.

As seen below, the error is at the level of the RegistrySaxParser class at the level of weblogic server.

This class is invoked by apache common digester (Version 2) which is used by Jasper.


Here is the error:

java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"> 

Here is the stack:

 <java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"> 

java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"

at javax.xml.parsers.SAXParserFactory.setSchema(

at weblogic.xml.jaxp.RegistrySAXParserFactory.setSchema(

at org.apache.commons.digester.Digester.getFactory(

at org.apache.commons.digester.Digester.setFeature(

at net.sf.jasperreports.engine.xml.JRXmlTemplateDigesterFactory.configureDigester(

at net.sf.jasperreports.engine.xml.JRXmlTemplateDigesterFactory.createDigester(

at net.sf.jasperreports.engine.xml.JRXmlTemplateLoader.loadTemplate(

at net.sf.jasperreports.engine.xml.JRXmlTemplateLoader.load(

at net.sf.jasperreports.engine.xml.JRXmlTemplateLoader.loadTemplate(

at net.sf.jasperreports.engine.fill.JRFillReportTemplate.loadTemplate(

at net.sf.jasperreports.engine.fill.JRFillReportTemplate.evaluate(

at net.sf.jasperreports.engine.fill.JRBaseFiller.collectTemplates(

at net.sf.jasperreports.engine.fill.JRBaseFiller.collectTemplateStyles(

at net.sf.jasperreports.engine.fill.JRBaseFiller.collectStyles(

at net.sf.jasperreports.engine.fill.JRBaseFiller.loadStyles(

at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(

at net.sf.jasperreports.engine.fill.BaseReportFiller.fill(

at net.sf.jasperreports.engine.fill.JRFiller.fill(

at net.sf.jasperreports.engine.fill.JRFiller.fill(

at net.sf.jasperreports.engine.JasperFillManager.fill(

at net.sf.jasperreports.engine.JasperFillManager.fillReport(




Have anyone faced a similar issue, are there any suggestion?

elio.khattar's picture
Joined: May 20 2022 - 10:11am
Last seen: 1 month 6 days ago

0 Answers:

No answers yet