DOM003 Namespace error

[Ian Roberts <ir...@decisionsoft.com>]

In Xerces-J 1.2.3, I've found that trying to import or validate against a
schema which contains

<!DOCTYPE schema SYSTEM 'http://www.w3.org/1999/XMLSchema.dtd'>

causes a DOM003 namespace error.  This does not happen with version 1.2.0,
which I was previously using.  Is this a known bug?  (I haven't been able
to test it with the latest CVS, as I can't get it to build).

Ian

-- 
Ian Roberts                     | irr@decisionsoft.com
DecisionSoft Ltd.               | http://www.decisionsoft.com/

Re: DOM003 Namespace error

[Ramesh Gupta <ra...@eNode.com>]

on 12/11/00 4:16 AM, Ian Roberts at irr@decisionsoft.com wrote:

> In Xerces-J 1.2.3, I've found that trying to import or validate against a
> schema which contains
> 
> <!DOCTYPE schema SYSTEM 'http://www.w3.org/1999/XMLSchema.dtd'>
> 
> causes a DOM003 namespace error.  This does not happen with version 1.2.0,
> which I was previously using.  Is this a known bug?  (I haven't been able
> to test it with the latest CVS, as I can't get it to build).
> 
> Ian

This problem was fixed after 1.2.3 was released. I am including a copy of
Arnaud's message in this regard. I verified the fix using 12/10 version of
the sources.

Ramesh

> ----------
> From: Arnaud Le Hors <le...@us.ibm.com>
> Organization: IBM
> Reply-To: xerces-j-dev@xml.apache.org
> Date: Thu, 07 Dec 2000 12:20:29 -0800
> To: xerces-j-dev@xml.apache.org
> Subject: Re: Namespace problems in Xerces-J 1.2.3
> 
> I just checked in a fix for that. It is yet another bug related to the
> fact that namespaces and DTDs just don't work together, and every time
> we fix something we break something else. It's a real nightmare. I'm
> certain that what we now have will still break in some cases. But fixing
> it isn't an easy task. Someone would need to completely revisit the
> namespace/DTD relationship in Xerces1. Thanksfully Xerces2 is in a much
> better shape here, because it was taken into account from the start.
> I believe I know what the right thing to do is, but I don't know if/when
> I'll have the time to make a thorough review of the code and fix it...
> -- 
> Arnaud  Le Hors - IBM Cupertino, XML Technology Group