Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Mon, 19 Mar 2001 12:08:12 -0500 (EST)
From: Donald Ball <balld@webslingerZ.com>
To: cocoon-dev <cocoon-dev@xml.apache.org>
Subject: Re: the "evil" document() function
In-Reply-To: <3AB6080A.5F3214C5@anyware-tech.com>
Message-ID: <Pine.LNX.4.30.0103191204160.7633-100000@rdu25-22-175.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 19 Mar 2001, Sylvain Wallez wrote:

> > Unfortunantly looks quite difficult: to make the Cocoon caching system work
> > okay the XSLT processor should somehow let _Cocoon_ know what
> > files it has included with document() function... Can't ivent any way
> > to pass this knowledge from XSLT procssor to Cocoon... :-(
>
> Trax provides the javax.xml.transform.URIResolver interface "that can be
> called by the processor to turn a URI used in document(), xsl:import, or
> xsl:include into a Source object" (copy-paste from Xalan's javadoc).
>
> Isn't just what's needed to notify Cocoon when "document()" is called ?
> A Cocoon implementation could track dependencies, cache documents,
> etc...

hmm. that might do it - if we create a special URIResolver class for each
stylesheet and add to the list of associated resources whenever the
resolve method is called, that would work. i wonder though - _must_ the
trax processor resolve URI's this way?

- donald


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org