Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Debugging XSLT called from external program (xsl:message output?)

From: p0 <yves.dhondt@-----.--->
To: NULL
Date: 6/21/2008 7:28:00 AM
Dear all,

I have a third-party program which calls a stylesheet and uses the
returned output. The application uses the MSXML engine to do the
transformations. Users are able to create their own stylesheets.

Documentation of the XSLT format is sketchy at best, so trying to
create my own stylesheet is rather difficult. I made one which does
what I want for now but I want to look a bit deeper into it.

My questions are:

1)Does MSXML allow somehow to debug the XSLT by stepping into it
whenever it is called from the external program? Like, could I use
Visual Studio 2008, put in some breakpoints, launch the app, and get
it to break into Visual Studio 2008 on the stylesheet calls?

2)As the third-party program does not output xsl:message contents,
does MSXML output it to somewhere by default? A simple file somewhere
on my drive? Or maybe an eventlog? Or could I instruct it to do so for
a while?

3)Is there a way to see what the XML is that is send together with the
XSLT to the transformation engine?

TIA,

Yves


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent