Hi Frank,
Another way you might consider doing this is by pipelining ... in the
first pass, transform into your output plus warnings/errors, then
pass the result into two separate processes, one that filters out the
warnings and the other that filters out the content.
This is a bit klugey, but doesn't take you into any extension
functions at all, and it can be set up with batch files written in
ancient languages if necessary.
Cheers,
Wendell
At 07:46 AM 9/21/2006, George wrote:
You can get (in general) the output of the xsl:message but you need
processor specific code for that. Also this requires configuring the
processor in a specific way, thus you need to have control over the
transformation execution.
Using xsl:result-document to output the some data to a file seems ok
to me, as you can do this directly from XSLT. Note that this works
only in XSLT 2.0, for XSLT 1.0 you can eventually use the specific
processors extensions for writing output documents.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--