Mon, 8 Oct 2007 10:28:01 -0400, /Michael Glavassevich/:
Can you open a JIRA issue (including your test) to track this problem?
Created XERCESJ-1273:
https://issues.apache.org/jira/browse/XERCESJ-1273
--
Stanimir
-
To unsubs
It looks like xjParse does what I need by specifying -S a.xsd -S b.xsd
etc on the command line, so I do still have a "no code" solution :)
The Xerces plugin for jEdit does also have the facility to import
catalog files, would I be right in assuming I can write a catalog file,
use that in jEd
As you said: Your original document is being parsed into Xalan's internal
DTM data model, which is MUCH more compact than the more common
Java-object-based DOM implementation. When you import it into a DOM, it's
likely to get larger; depending on the structure of the document and the
details of th
Normally, you would specify a canonical schema location. This might
just be the name of the file or some official qualified
name. Usually, a URL is used, which sometimes actually points to a
location where the file can be downloaded. By hosting the file at a
live URL, users can use this ca