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: Can I stop SAX validation from resolving non-approved
   namespaces?

Re: Can I stop SAX validation from resolving non-approved
   namespaces?

2003-04-16       - By Simon Kitching

On Wed, 2003-04-16 at 19:24, Andy Taylor wrote:
> Hi Jeff,
>
> I understand this, but I would like to stop the validation process
> (which, I believe, will run through the entire document resolving
> entities BEFORE using my SAX ContentHandler Interface) from accessing
> DTDs and schemas on unknown machines.
>
> The only way I can think of doing this would be to parse the document
> twice - first with validation off so I can spot any "unapproved"
> namespaces. If all namespaces are OK, I can then parse the document
> again with validation on. This seems like a bit of a waste of time!

This should not be necessary.

When a document is being parsed, and a namespace is encountered, then
the registered EntityResolver is *immediately* called, passing the
namespace URI.

The entity resolver can inspect this URI, and do any of the following
(on a per-uri basis):

(a) return null, causing xerces to do its default behaviour which is to
attempt to load the document referenced by the URI.

(b) return an input stream for any source of data you wish. this is how
to implement a local "cache" of schemas/dtds :- look up a mapping of
uri->local-file-name and return the contents of the local file. Xerces
will then accept this data *instead of* fetching from the original uri.

(c) throw an exception. This will cancel any further processing of the
document. This, I believe, is what you want to do if an unknown URI is
encountered.


As Jeff said, the xsi:schemaLocation is a hint; basically it sets up an
EntityResolver which looks up the uri in the list of (uri->file)
mappings in the xsi:schemaLocation. If a match is found, it returns the
corresponding file. However if a match is not found, it returns null
causing Xerces to try to fetch the remote file - which is not what you
want.

Implementing an EntityResolver to do what you wish is about 50 lines of
code - not a big deal.

> >From: "Jeff Greif"
> >Reply-To: xerces-j-user@(protected)
> >To:
> >Subject: Re: Can I stop SAX validation from resolving non-approved
> namespaces?
> >Date: Tue, 15 Apr 2003 09:52:37 -0700
> >
> >No. The xsi:schemaLocation attribute is just a hint to the parser
> about where to find the schema. If you attach an EntityResolver to the
> parser (in its constructor, or by some method like setEntityResolver)
> you have complete control of how any URIs are looked up. You can
> resolve particular namespaces to your fixed copy of the schemas in
> question (and can make local copies of common ones found on the
> Internet to avoid redundant network activity).




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