org.xml.sax.SAXNotSupportedException

By: Eric Carlson - ericcarlson
org.xml.sax.SAXNotSupportedException
2002-03-22 01:15
org.xml.sax.SAXNotSupportedException: http://xml.org/sax/features/validation

I'm getting that exception with resin 2.0.5 when jasper executes this:
XMLReader xmlReader = XMLReaderFactory.createXMLReader();
xmlReader.setFeature("http://xml.org/sax/features/validation", true);

Resin uses its own XML parser which I suppose I could kick but I was wondering if there is a param I could use to disable validation instead?
It seems a little final hardcoding the "true" in JRXmlLoader.java in this way...

It would be more flexible to validate during development but turn off for production (in a closed environment).


By: Dave Cook - butsafire
RE: org.xml.sax.SAXNotSupportedException
2002-03-22 06:53
Hi:
Yes, I have the same problem. I too use Resin and the parsers are conflicting. Unfortunately, I have other code written to the Resin parser as well. I have an odd thing happening. When I boot the server and load Resin, my own code works but Jasper won't. Then if I shell out and do a /etc/init.d/resin restart, my Jasper reports funtion fine. (I'm running my reports from the Web via .JSP scripts)
Dave.


By: Teodor Danciu - teodord
RE: org.xml.sax.SAXNotSupportedException
2002-03-25 07:50

Hi,

For the moment there is no such flag to turn
the validation off.
Maybe in the future versions.

However, you should note that the intended way
to use JasperReports is to create your XML report
design and compile it once, in the development
phase, not every time you run the report.
It's just like you would have an application that
generates java source code that you compile every
time you run it.

The report designs should be fixed and only data
should change with every execution.
Instead of generating report designs at runtime
you should create special data sources if the
default ones are not flexible enough.

Thanks,
Teodor



By: Teodor Danciu - teodord
RE: org.xml.sax.SAXNotSupportedException
2002-11-06 13:49

Hi,

This is now possible in 0.4.3 by setting the
jasper.reports.compile.xml.validation
system property to false.

http://jasperreports.sourceforge.net/quick.how.to.html#compile

Thank you,
Teodor