error handling in schema validation

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

error handling in schema validation

error handling in schema validation

2003-01-09 - By Kiran Bhumana

Reply: 1 2

I have it fixed .

I had the contentHandler set and not ErrorHandler
setErrorHandler was what I missed.

-----Original Message-----
From: Kiran Bhumana
Sent: Thursday, January 09, 2003 4:00 PM
To: xerces-j-user@(protected)
Subject: error handling in schema validation

I am trying to trap the errors being printed to the screen, during
validation by
overwriting the methods of the import
org.xml.sax.helpers.DefaultHandler;.

The errors look like this, but they don't seem to be going through the
apis
Such as,
public void error (SAXParseException e)
throws SAXException
{
System.out.println ("in error ");
errorStringList.append(e.toString());
}

public void fatalError (SAXParseException e)
throws SAXException
{
System.out.println ("in Fatal error ");
errorStringList.append(e.toString());
// throw e;
}

the errors printed onto the screen are,

shiporder
orderperson
[Error] shiporder.xml:6:9: cvc-complex-type.2.4.a: Invalid content
starting with elem
ent 'name'. The content must match
'(("":orderperson),("":shipto),("":item){1-UNBOUND
ED})'.
name
address
city
country
[Fatal Error] shiporder.xml:10:4: The element type "shiporder" must be
terminated by
the matching end-tag "</shiporder>".
org.xml.sax.SAXParseException: The element type "shiporder" must be
terminated by the
matching end-tag "</shiporder>".

What am I missing something here ?

Thank you,
Kiran B.

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas
-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office
:smarttags" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">

<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="cid:filelist.xml@(protected)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="time"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="date"/>

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>

<div class=Section1>

I have it fixed .
<o:p></o:p>

<o:p> </o:p>

I had the contentHandler
set and not ErrorHandler <o:p></o:p>

setErrorHandler was what
I missed. <o:p></o:p>

<o:p> </o:p>

-----Original Message----- 
From: Kiran Bhumana 
Sent: <st1:date
Month="1" Day="9" Year="2003">Thursday, January 09, 2003</st1:date>
 <st1:time
Hour="16" Minute="0">4:00 PM</st1:time>
 
To: xerces-j-user@(protected)
 
Subject: error handling in schema
validation

<o:p> </o:p>

<o:p> </o:p>

I am trying to trap the errors being
printed to the screen, during validation by <o:p></o:p>

overwriting the methods of the
import org.xml.sax.helpers.DefaultHandler;.<o:p></o:p>

<o:p> </o:p>

The errors look like this, but they
don’t seem to be going through the apis <o:p></o:p>

Such as, <o:p></o:p>

&nbsp
;  
public void error (SAXParseException e)<o:p></o:p>

 
           throws
SAXException<o:p></o:p>

&nbsp
;  
{<o:p></o:p>

 
           System.out
.println
("in error ");<o:p></o:p>

 
           errorStringList.append(e.toString());<o:p></o:p>

&nbsp
;  
}<o:p></o:p>

&nbsp
;  
<o:p></o:p>

public void fatalError
(SAXParseException e)<o:p></o:p>

 
           throws
SAXException<o:p></o:p>

&nbsp
;  
{<o:p></o:p>

 
           System.out
.println
("in Fatal error ");<o:p></o:p>

 
           errorStringList.append(e.toString());<o:p></o:p>

 
           //         
throw e;<o:p></o:p>

&nbsp
;  
}<o:p></o:p>

<o:p> </o:p>

the errors printed onto the screen
are,  <o:p></o:p>

<o:p> </o:p>

shiporder<o:p></o:p>

orderperson<o:p></o:p>



[Error] shiporder.xml:6:9:
cvc-complex-type.2.4.a: Invalid content starting with elem<o:p></o:p>


ent 'name'. The content
must match
'(("":orderperson),("":shipto),("":item){1
-UNBOUND<o:p></o:p>


ED})'.<o:p></o:p>

name<o:p></o:p>

address<o:p></o:p>

city<o:p></o:p>

country<o:p></o:p>


[Fatal Error]
shiporder.xml:10:4: The element type "shiporder" must be terminated
by<o:p></o:p>


the matching end-tag
"</shiporder>".<o:p></o:p>


org.xml.sax
.SAXParseException:
The element type "shiporder" must be terminated by the<o:p></o:p>


 matching end-tag
"</shiporder>".<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p>

What am I missing something here ?<o
:p></o:p>

<o:p> </o:p>

Thank you,<o:p></o:p>

Kiran B.<o:p></o:p>

<o:p> </o:p>

</div>

</body>

</html>