Hi, As you know oXygen 4.0 will add as main feature an XSLT debugger. We have available a beta version of the all platforms distribution. Please download it from: http://www.oxygenxml.com/update/oxygenAll4.0B.tar.gz and use the following license: =================== Registration_Name=Betatester Company=Syncro Soft Ltd. Category=Professional Component=XML-Editor, XSLT-Debugger Version=4, 4 Number_of_Licenses=1 Date=04-07-2004 Duration=31 SGN=MC0CFQCCP1yEBWUtQvAMpD8y1AdTlt1IUwIUWegwL8YgkkCyzke84q+a5PMYc2o\= =================== Below there is a list of the debugger features. Along with these features there are also a lot of improvements in the editor part but they are not extracted yet from bugzilla. XSLTDebugger features: * Support for Saxon and Xalan XSLT engines. * Stepping capabilities: step in, step over, step out, run, run to cursor, run to end, pause, stop. * Breakpoints on both source and style documents. * Call stack view on both source and style documents. * Trace history on both source and style documents. * Support for XPath expression evaluation during debugging. * Step into imported/included stylesheets as well as included source entities. * Available template and hit count. * Variables view. * Dynamic output generation. Details: * Support for Saxon and Xalan XSLT engines. The debugger supports both Saxon 6.5.3 and Xalan 2.5.1 engines. * Stepping capabilities. Step in: goes to the next stylesheet node. (next step in transformation) Step over: skip the next stylesheet node (including its sub-elements). The debugger will stop on the next sibling element. Step out: steps out to the next sibling of the stylesheet parent node. If this not exists,steps out to the next node at the same level as the parent, or higher. Run: run the debug transformation run until either an enabled breakpoint is encountered (in source or stylesheet) or the end of transformation occurs. Run to cursor: run the transformation until the execution reach the line on which the cursor is currently in. Run to end: run the transformation till end, without taking into account any enabled breakpoint which might be set. Pause: interrupt the current transformation. This is useful for long transformation (Docbook like) when you want to find out in what point the transformation is. The transformation can be resumed after. Stop: end immediately the transformation process. * Breakpoints on both source and style documents. You can set breakpoints both on xml or xsl documents iterated by the transformation. * Call stack view on both source and style documents. At any point during debugging, you can see the current stack for both stylesheet and source elements. * Trace history on both source and styleasheet documents. During debugging you get the full trace history of transformation on both source or stylesheet documents. * Support for XPath expression evaluation during debugging. You can evaluate XPath expression during debugging by defining watch expressions. The debugger will update its value during stepping. (the expression are evaluated in the current context). * Step into imported/included stylesheets as well as included source entities. Once a xml entity or an imported/included stylesheet is about to be used by the transformation, you will get access to it in order to see were the current step is. * Available template and hit count. You get a list with all templates used during transformation and their correspondent number of hits. * Variables and parameters view. The debugger list all variables and parameters together with their scope and actual value. * Dynamic output generation. The output is generated dynamically during the stylesheet execution All the best, George ------------------------------------------------------------- George Cristian Bina mailto:george@oxygenxml.com <oXygen/> XML Editor - http://www.oxygenxml.com/