- From: Wendell Piez <wapiez@mulberrytech.com>
- Date: Fri, 16 Apr 2010 11:02:04 -0400
- To: xproc-dev@w3.org
Hi,
I also have a question that bears on debugging, but debugging the
pipeline not the XProc as such.
As you know, I have multiple passes in XSLT. Say, three:
<p:pipeline xmlns:p="http://www.w3.org/ns/xproc"
version="1.0" name="triple-play">
<p:xslt>
<p:input port="stylesheet">
<p:document href="transform1.xsl"/>
</p:input>
</p:xslt>
<p:xslt>
<p:input port="stylesheet">
<p:document href="transform2.xsl"/>
</p:input>
</p:xslt>
<p:xslt>
<p:input port="stylesheet">
<p:document href="transform3.xsl"/>
</p:input>
</p:xslt>
</p:pipeline>
I am guessing if I made this into p:declare-step, I could have ports
to show me the intermediate results after each transformation.
But I don't always want to see them, only sometimes.
Currently I have achieved this using three different XProc instances,
each importing the previous in a cascade, so if I want to see
intermediate results, I run the appropriate XProc. But this is
suboptimal for several reasons.
I have a couple of ideas for things to try, but maybe I'm better off
just asking what the best methods are?
In effect I'd like to implement a "production" and a "debugging"
mode, with options to show me any or all the intermediate results in
addition to or instead of the final result.
Gratefully as always,
Wendell
======================================================================
Wendell Piez mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
Received on Friday, 16 April 2010 15:02:43 UTC