Re: [xsl] XMLPipe model: should we change the name?

Subject: Re: [xsl] XMLPipe model: should we change the name?
From: S Woodside <sbwoodside@xxxxxxxxx>
Date: Sat, 22 Feb 2003 13:46:38 -0500
On Saturday, February 22, 2003, at 01:09 PM, Michael Pediaditakis wrote:

E.g. if we have a tranformation that handled an <import> element (with
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.

axkit 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.

it also allows substantial code reuse becuase you can call /foo/bar.xml directly as a file and get the processed result, set it up that way, and then reuse the results in any pipeline that calls axkit:/foo/bar without writing additional handling code.

I hope that makes sense.


-- -- 99% Devil, 1% Angel

XSL-List info and archive:

Current Thread