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.
The Xerces XMLSchema infoset

The Xerces XMLSchema infoset

2004-02-10       - By Mik Lernout

Dear,

Maybe a little background first:
I am in process of delivering a XOM-like java library to XMLSchema called
'endymion', that will be released under LGPL
as part of the 'narcissus'-project. The goal of the API is to offer a heavily
typed, java-like and simple access to the information
embedded in an XMLSchema.

At first I started of with parsing XMLSchema myself, but surrendered after a
while becaause of the complexity it brough upon combined
with the apparent liberal interpretations of the XMLSchema spec of some other
parsers. I decided on the XMLSchema infoset model (org.apache.xs.*)
in Xerces because it is light, has active developers and tries to adhere to
specs.

But, of course, I am encountering some issues (let's call them challenges :-))

* I would like to validate XML to specific complex types in XMLSchema's. (so
without them being declared as XMLSchema instances...) I would also like to be
able to validate in memory DOM document trees / XOM document trees / JDOM
document trees / SAX parse events with a non Xerces parser /...
I think I am familiar enough with the Xerces internals to know that this should
not be that difficult. For example for the SAX Parser
I would only need to simulate an XNI-pass by making an adapter class that
implements DefaultHandler and translates all events to a XMLDocumentValidator
as if in a a XNI-pipeline. This adapter class seems to be pretty generic (can
make all XNI - XMLDocumentHandler act upon SAX events except for XNI events)
that I was wondering if it didn't already exist, or if somebody could give me
some tips with regards to this.

* I see that in CVS there have been several changes / updates with regards to
the visibility of fields and methods in several API classes. I was wondering
if there is a certain goal or reason for permorming these changes and when they
are finished / released. It would be really cool to have some public hooks
into the org.apache.xerces.impl.dv.xs.* - value-classes to be able to access
the actual values of DecimalDV and others.

I am very eager to contribute back any bug fixes / changes that I will develop
so even if you only have some guidelines as opposed to full fledged
solutions I will be very happy...

Mik

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