Neil,
I made a naïve implementation of an EntityResolver that only uses the
absolute paths of the SystemIds it receives, but this doesn't work for
the following reasons:
The main schema file includes ~20 other schema files which are located
in other directories using relative paths and each one o
OK,
Well, ask a stupid question, get a good answer :)
Elisha
> -Original Message-
> From: Neil Graham [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 31, 2005 12:54 PM
> To: c-dev@xerces.apache.org
> Subject: RE: Xerces issues handling recursive schema includes
>
> Hi Elisha,
>
>
>
Hi Elisha,
"Elisha Berns" <[EMAIL PROTECTED]> wrote on 10/31/2005 02:52:49 PM:
> Hi Neil,
>
> Thanks for the reply. Just one question about this. The schema in
> question includes tens of other schema files using relative URIs (they
> all exist in a large directory structure). So by what y
Hi Neil,
Thanks for the reply. Just one question about this. The schema in
question includes tens of other schema files using relative URIs (they
all exist in a large directory structure). So by what you write
"that system identifier fields are always set to the same value"
presumably you mea
Hi Elisha,
Recursive, or circular, includes are supposed to be handled properly by a
schema parser. While I'm not really active anymore on the code base, this
question does come up periodically, usually in the context of a set of
schemas that get loaded purely via schemaLocation hints, or via
[
http://issues.apache.org/jira/browse/XERCESC-1479?page=comments#action_12356424
]
Alberto Massari commented on XERCESC-1479:
--
You are right, the presence of the '+' allow the method to look for
non-DOMNode-derived interfaces, but doesn't exclude
Error in regexpr matching
-
Key: XERCESC-1521
URL: http://issues.apache.org/jira/browse/XERCESC-1521
Project: Xerces-C++
Type: Bug
Components: Validating Parser (Schema) (Xerces 1.5 or up only)
Versions: 2.7.0
Environment: Windows
[
http://issues.apache.org/jira/browse/XERCESC-1479?page=comments#action_12356410
]
Tobias Schuette commented on XERCESC-1479:
--
the changes to DOM(Attr/ElementNS)Impl::isSupported look straight forward,
but the changes commited to DOMDocumentTypeIm
