Xslt processor windows gui

Active Oldest Votes. Edit: Since people are having issues reading the comment section. Improve this answer. I gave you the first a deserved upvote, thank you for this! Is there a free version?

This is not a free tool — nZeus. Posted in x — user Show 5 more comments. Dynamic intellisense: prompting with template names or with modes or with parameter names. XSLT 2. One-click invocation of many XSLT processors. Dimitre Novatchev Dimitre Novatchev k 26 26 gold badges silver badges bronze badges. Good tool BUT it won't work in 64bit : — nixon. The only thing is that in most OSes you must run it as administator -- it is convenient to change the properties or have a shortcut with properties set to "run as administrator.

DimitreNovatchev Where is it now? Project playing hide and seek with us? The following table describes the predefined context variables used by the XSLT debugger. The Output window shows any error messages or security exceptions that occur during debugging.

It also shows debugger output. The Task List lists all the compilation errors in the style sheet. Double-clicking the error takes the cursor to the line with the error. The Breakpoints window shows all breakpoints set in the current project. If a breakpoint is added while the window is in view, the window is automatically updated to show the new breakpoint.

The variables displayed in the Watch window are for the current context the top-most item on the call stack. If you change the context, the watch window updates and displays variables set for that context. The Call Stack window is used to view the names of functions on the call stack, parameter types, and parameter values. Call stack information is shown only when the program being debugged is in a break state. The call stack represents the various contexts that the XSLT execution is going through.

For example, if there is a call from template "a" to template "b", template "a" and template "b" appear in the Call Stack window with the current context at the top of the list.

The user is able to see the query that is currently executing. Clicking an item other than the one at the top of the list indicates to the viewer where the XSLT execution branch happened using the standard green highlighting and green arrows.

The Java runtime system is available for download from Sun Microsystems, Inc. If you have a different platform UNIX or Mac, for instance , then you need to contact your OS vendor to see if they make available an up-to-date Java runtime environment.

Saxon is distributed as a zip file, so you need to unzip it into some suitable location. It can be a temporary location because you can move the few files you really need to a new location. To run Saxon, you only need to tell your Java processor where the Saxon. There are three files in the directory you unpacked Saxon into:. You will not need saxon-fop. The DocBook stylesheets have some custom extension functions written specifically for the Saxon processor.

These functions are contained in a saxon There may be several saxon jar files there, labeled by the version number of Saxon. Use the one closest to your Saxon version number. You want the Xerces2 Java parser. The web page has a link to where you can download just the latest jar file, xercesImpl. Put the file in a convenient location. You need to include the full path to the necessary. That environment variable is used by the Java processor to locate compiled code used by Java programs.

You can copy the. If it does not already exist in the list, then select New. Each path should be a full path to one of the required.

For example:. If you are already in a DOS window, you will need to exit and restart it for the new environment variable to take effect. This should report the version of Saxon that you have installed, as well as usage and command options. Saxon is a Java application that is executed from a command line.

In order for the command to find all the Java code it needs, you must add the Java. Once you have done that, then you execute the java command as follows. The backslashes mean the line continues without break, but is shown here on separate lines for clarity. Note that the XML document name precedes the stylesheet path in a Saxon command line.

You can put any Saxon options such as -o before the document filename. You can also set any number of stylesheet parameters such as use. See Chapter 6, Using stylesheet parameters for details on using parameters. The section on installing Saxon included an optional step for downloading the Xerces parser. Once you have added the path to xercesImpl.

These -D options must appear before the com. StyleSheet class name. The options will fail if the xercesImpl. The DocBook Saxon and Xalan extensions are not enabled by default. They are enabled by setting various stylesheet parameters. See Chapter 6, Using stylesheet parameters to learn how to set stylesheet parameters. Each extension has its own stylesheet parameter, and they are all set to 1 on by default.

However, they are not actually turned on by default because the overall use. To use any of the extensions, set the use. The following is a list of the functions and their enabling parameters. If you are not using any of these features in your documents, then you have no need to turn on the extensions. However, there is no harm in turning them on. Xalan's installation process depends on which version of the Java runtime you will be using to run it.

In Java 1. Unfortunately, the version that was bundled was superceded by improved versions from Apache. Most people preferred the newer versions, but they required taking some extra steps to make sure the bundled version was not being used instead. In the following procedure, any extra steps needed for Java 1. Xalan is very easy to install because it is a Java program and requires no compiling. Since Xalan-J requires a Java runtime environment, you might need to obtain or update your Java setup before Xalan will work.

You probably will not want the latest experimental version. They provide. That site will also provide you with detailed instructions for getting started with Xalan. As of version 2. Either one will work for DocBook processing. Xalan is distributed as a zip file, so you need to unzip it into some suitable location. To run Xalan, you only need to tell your Java processor where the Xalan. The bin directory in the directory you unpacked Xalan into will contain the three files you need:. Sample application using Xalan in a Java servlet.

This file is not needed for DocBook processing.