You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Uma Shinde <us...@openmarket.com> on 2000/10/30 21:46:41 UTC
Entity Resolver for "included" dtds..
The default behavior for entityResolver fetches the DTD specified in the
!DOCTYPE from SystemID. But if that DTD includes another DTD, as
<!ENTITY.."xyz.dtd">, entityResolver isn't able to resolve that and results
in a dtd not found error.
How do I resolve this issue?
-Uma
Re: Entity Resolver for "included" dtds..
Posted by Luke Blanshard <lu...@quiq.com>.
Uma Shinde wrote:
> The default behavior for entityResolver fetches the DTD specified in the
> !DOCTYPE from SystemID. But if that DTD includes another DTD, as
> <!ENTITY.."xyz.dtd">, entityResolver isn't able to resolve that and results
> in a dtd not found error.
Here's how we handle it. The top of our outer DTD contains these lines to
include the inner DTD:
<!ENTITY % expert PUBLIC
"-//Quiq, Inc//ENTITIES Common list structures//EN"
"../expert.dtd">
%expert;
Luke
Re: Entity Resolver for "included" dtds..
Posted by Eric Ye <er...@locus.apache.org>.
Go ahead and submit the changes to the list. I'd be more than happy to take
a look at it.
_____
Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org
----- Original Message -----
From: "Jerry Lawson" <je...@virtualsummit.com>
To: <xe...@xml.apache.org>
Sent: Monday, October 30, 2000 1:36 PM
Subject: Re: Entity Resolver for "included" dtds..
> This question came up a couple weeks ago relative to
> the <include declaration for schemas. The problem there
> is TraverseSchema.java has its own EntityResolver, but doesn't
> have any way of first trying the user-defined EntityResolver
> provided to the SAXParser or DOMParser.
>
> Would it be acceptable to this list if I submitted changes to
> allow the user-defined EntityResolver to flow down into
> TraverseSchema.java, which would use that object before trying
> its own local EntityResolver ?
> (I would, of course, expect Eric, Andy or Jeff to verify...)
>
> Uma Shinde wrote:
> >
> > The default behavior for entityResolver fetches the DTD specified in the
> > !DOCTYPE from SystemID. But if that DTD includes another DTD, as
> > <!ENTITY.."xyz.dtd">, entityResolver isn't able to resolve that and
results
> > in a dtd not found error.
> >
> > How do I resolve this issue?
> > -Uma
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
> --
> ___________________________________________________
> Jerry Lawson Virtual Summit, Inc.
> Virtual Programmer jerry.lawson@virtualsummit.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
Re: Entity Resolver for "included" dtds..
Posted by Jerry Lawson <je...@virtualsummit.com>.
This question came up a couple weeks ago relative to
the <include declaration for schemas. The problem there
is TraverseSchema.java has its own EntityResolver, but doesn't
have any way of first trying the user-defined EntityResolver
provided to the SAXParser or DOMParser.
Would it be acceptable to this list if I submitted changes to
allow the user-defined EntityResolver to flow down into
TraverseSchema.java, which would use that object before trying
its own local EntityResolver ?
(I would, of course, expect Eric, Andy or Jeff to verify...)
Uma Shinde wrote:
>
> The default behavior for entityResolver fetches the DTD specified in the
> !DOCTYPE from SystemID. But if that DTD includes another DTD, as
> <!ENTITY.."xyz.dtd">, entityResolver isn't able to resolve that and results
> in a dtd not found error.
>
> How do I resolve this issue?
> -Uma
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
--
___________________________________________________
Jerry Lawson Virtual Summit, Inc.
Virtual Programmer jerry.lawson@virtualsummit.com