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.
XInclude exceptions - how to mirror Xerces J functionality into Xerces C++?

XInclude exceptions - how to mirror Xerces J functionality into Xerces C++?

2007-02-04       - By Michael Glavassevich
Reply:     1     2     3     4  

Hi Simon,

Simon Rowland <srowlandx11@(protected)> wrote on 02/03/2007 05:45:21 PM:

> Hi there,
>
> I'm writing an XInclude module for the Xerces C++ parser. Currently I am

> writing a DOMDocument -> DOMDocument transformer. Next I will write a
> SAX filter to do it live in the parse.
>
> I have a quick question about the Xerces-J implementation and it's
> Exceptions. Basically I want to propagate XInclude error messages out of

> my module into the client application.
>
> My current thinking is to create a sublcass of XMLException, as many
> other Xerces C++ internal errors do (e.g. PlatformUtils etc). This is
> also the closest thing I can spot to a similar mechanism to the Xerces J

> XInclude code, which uses a XMLParseException which is a sublcass of the

> generic XNIException.
>
> My understanding of the spec is that it doesn't specify what we use, as
> long as we stop doing the XInclude when we encounter a fatal error.

The XInclude spec doesn't say but the various XML APIs (SAX, DOM, JAXP,
StAX, etc...) do specify how errors are reported. Xerces-J's internal
error reporting mechanism was designed so that it could support them. This
includes reporting the error to a registered error handler and throwing an
exception with location information (e.g. SAXParseException and
XMLStreamException) up to the application if the error was fatal or if the
error handler threw an exception. If you're planning to add XInclude
support to Xerces-C++ as a new SAX/DOM parser feature [1] and/or as a new
parameter [2] for DOM normalization [3] you should use the error reporting
mechanisms which already exist for these APIs.

> So any advice from those that have been down the XInclude investgiation
> route already? Anything gratefully received!
>
> Many thanks in advance, Simon Rowland.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
> For additional commands, e-mail: j-dev-help@(protected)

[1] http://xerces.apache.org/xerces2-j/features.html#xinclude
[2]
http://xerces.apache.org/xerces2-j/javadocs/api/org/w3c/dom/DOMConfiguration
.html
[3]
http://xerces.apache.org/xerces2-j/javadocs/api/org/w3c/dom/Document.html
#normalizeDocument()


Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@(protected)
E-mail: mrglavas@(protected)

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