RE: Conditinally including an XSL module
Mike Kay: >So what's the underlying requirement that people would like a "run-time >include" to satisfy? Presumably it's to have a different set of template >rules depending on what you find in the source document, and perhaps to have >different sets of template rules in force at different times. I think you are right (in the general case). I think the reason is that one would like to have only one stylesheet for a whole system, even though the system contains different documents with somewhat different processing requirements. I had a similar need in which depending on the source document I definitely needed different templates, and the most natural way of writing them would have used mostly the same element names and structures even though the results would have to be (somewhat) different in the two cases. I ended up creating separate high level stylesheets for each "run-time" situation. These were very brief, because each of them could statically include all the templates that were common to them all. Then I also had separate includes for the templates that were unique to each "run-time" situation. The main reason why I would have liked to avoid this, though, was that (as far as I know), this means some thrashing if my xml's come through the system at random, so that first I'd need one stylesheet, then the other. It would be nice if there could only be one stylesheet that would stay resident in memory as the system processed multiple documents. Rick Suiter XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format