Subject: Re: [xsl] XMLPipe model: should we change the name?|
From: S Woodside <sbwoodside@xxxxxxxxx>
Date: Sat, 22 Feb 2003 13:46:38 -0500
E.g. if we have a tranformation that handled an <import> element (withaxkit has just introduced a new mechanism in 1.6.1 that I think might help with your problem. it also allows significant code re-use for me. It is the "axkit:" url that you can use in document() calls. if you call, e.g., document("axkit:/foo/bar.xml') axkit will first apply any XSLT to foo/bar.xml that is either designated in the processing instructions in bar.xml, or in the Apache configuration directives for /foo/bar.xml. Thus you would avoid the case, where the included file contains unprocessed XML includes or the like, because the PI'd XSLT would take care of that first.
functionality similar to XML Inclusions) and we have other tranformations
that might generate additional <import> elements. In that case a simple
static pipeline is not sufficient.
-- www.simonwoodside.com -- 99% Devil, 1% Angel