Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Re: How do I get an XMLReader to stop parsing when the XSD
   validation fails

Re: How do I get an XMLReader to stop parsing when the XSD
   validation fails

2003-04-14       - By Richard Rowell

On Mon, 2003-04-14 at 13:54, Ahearn, Denis wrote:
> Hello,
>
> Is there a way to have the XMLReader.parse()  method stop if the XML
> file being parsed is invalid with respect to an associated XML schema
> (XSD)?  I have poured through the online documentation as well as the
> Xerces JavaDocs, and didn't find anything that would allow me to
> control this behavior.  
>
> I have the following features in my XMLReader set to "on".
>
> http://xml.org/sax/features/validation
> http://apache.org/xml/features/validation/schema
> http://apache.org/xml/features/validation/schema-full-checking
>
> When running with an XML file that has some schema errors in it, I do
> see the validation errors being logged to my console window, however
> the XMLReader still parses the XML file.  In this case, I would like
> to be able to avoid processing the file (i.e. not do anything with the
> data in the file), and instead inform the user that the XML file
> contains validation errors and the program can't proceed.

I'm not Xerces expert, so there may be a simpler way, but...

Couldnt you register your own custom error handler, and simply kill the
thread after you log/report the error?  IE:

public class MySAXApp extends DefaultHandler
{
 public MySAXApp (){ super();}
 public void startDocument (){}
 ...//other methods here
 public void error(SAXParseException e)
 {
   System.out.println("** " +e.getMessage() + " **");
   System.out.println("LINE: " + e.getLineNumber());
   System.out.println("PUBLIC_ID: " + e.getPublicId());
   System.out.println("SYSTEM_ID: " + e.getSystemId());
   System.exit();
 }
 publiv static void main()
 {
   XMLReader xr = new SAXParser();    
   ...//turn on options here
   MySAXApp handler = new MySAXApp();
   xr.setErrorHandler(handler);
   ...//parse here
  }

If the call to system.exit() isn't elegant enough for your tastes, You
may alternatively be able to throw an exception in the error() function
and catch it outside the call to parse() (I haven't tried this though).

--
Richard Rowell <richard@(protected)>


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)