[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Concat dynamically assigned xslt
I would not create a huge, dynamically created XSLT. Cocoon offers you
aggregation or CInclude/XInclude. So I would transform the output of the
transformer for example to the following:
<PAGE> <xi:include href="cocoon:/abstract1-first"/> ... <xi:include href="cocoon:/abstract5-fifth"/> </PAGE> The generator would then give only the information how to get the content of the abstract and the name of the xsl. The sitemap would match on this: <map:match pattern="abstract*-*"> <map:generate src="content-abstract{1}"/> <map:transform src="stylesheets/{2}.xsl"/> <map:serialize type="xml"/> </map:match> So every abstract is transformed separately and aggregated at the end to a "big thing". Your original abstract pipeline I would change to: <map:match pattern="abstractpage_*.html"> <map:generate src="getEveryMetaInfoFromDBAsXML.xsp"/> <map:transform src="transformers/convertMetaInfo2XInclude.xsl"/> <map:transform type="xinclude"/> <map:transform src="stylesheets/maybeSomePostProcessing.xsl"/> <map:serialize type="html"/> </map:match> So the whole processing is not a XSLT problem, but a solvable Cocoon problem. Is the propagated way an option? Or is your way already fixed? Regards, Joerg Robert Sösemann wrote: I am not sure if this is a cocoon specific problem or solveable with XSL only. I have this problem. 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
|