Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 92677 invoked by uid 500); 3 May 2001 21:59:14 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 92611 invoked from network); 3 May 2001 21:58:57 -0000 Date: Thu, 3 May 2001 23:37:15 +0200 (CEST) From: giacomo X-X-Sender: To: Subject: Re: [Fwd: Re: C2: Sitemaps and DTD's] In-Reply-To: <3AF1C030.A0E078F4@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Thu, 3 May 2001, Berin Loritsch wrote: > giacomo wrote: > > > > On Thu, 3 May 2001, Berin Loritsch wrote: > > > > > Here is an issue that was brought up by someone on the Cocoon Users list. > > > > > > They have a DTD that they want a document to use (because of ENTITY declarations > > > and such). The tool they are using to create the XML documents uses absolute > > > paths so it is difficult to move these documents from one machine to another. > > > > > > The solution I gave him will work, but the cost is pretty high (look below). > > > Is there anyway, we can configure an EntityResolver with pre-mapped DTDs? > > > IOW can we initialize the Parser to use local copies of a DTD without opening > > > a port to the same server and using network protocols to obtain a local DTD? > > > > > > I don't know if this would promote EntityResolver to a Component Status, but > > > it might be useful: > > > > Are you talking about a separate EntityResolver or "the" EntityResolver > > encorporated into the Environment object? > > I was thinking "the" EntityResolver. Reason being that if our version of the > EntityResolver were componentized, we would be able to integrate URLFactory > psuedo-protocols and predeclare DTD mappings. > > I must admit to a certain level of ignorance with the EntityResolver. Having > never used it, I am not sure exactly what it is supposed to do or how it is > supposed to operate. It has todo with sub sitemaps contexts where "the" EntityResolver is capable to resolve a 'src="foo/bar"' onto a InputSource object pointing to the current context root path. Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org