[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: xslt 3.0 possible feature - some sort of collectio
Andrew,
This doesn't speak to the requirement itself (which seems perfectly legit to me), but only to the use case. One approach to achieving the aims here is to reverse the order of operations. The first pass doesn't emit the messages, but simply generates elements in a namespace reserved for the purpose. The second pass strips them out, while emitting messages for them as it goes. This approach works well when you are not set on using xsl:message as the reporting channel. For example, the messages can instead be siphoned to a separate document. Or, as you suggest, higher-level analysis of the message set can be conducted. Needless to say, this is all a piece of cake in XSLT 2.0 with or without XProc. Or if you like, two pieces of cake. Cheers, Wendell On 3/10/2011 1:28 PM, Andrew Welch wrote: Often we 'hack' xsl:message to output some information to post process later, and it struck me that it would be useful to have a way of accessing what has been sent to xsl:message during the same transform. This would be especially useful when streaming, as processing the data twice for different purposes is less than ideal.
|
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
|