http://xml.apache.org/http://www.apache.org/http://www.w3.org/

Overview

Downloads
Getting Started

FAQs

Sample Apps
Command Line
Usage Patterns

C++ API

Extensions
Extensions Library

Release Notes

Bugs
Testing

Downloading what you need
 

For Xalan-C++ version 1.4, we are distributing a Windows32 Visual C++ build and 5 UNIX builds with makefiles: a Red Hat Linux GNU build, an AIX xlC build, an HP-UX 11 aCC 32-bit build, an HP-UX 11 aCC 64-bit build, and a Solaris build. Please contact us at Xalan Development Mailing List if you would like to help provide builds for other platforms.

If you do not already have it, you must also download the Xerces-C++ 2.1.0 build as indicated below.

NoteThe Xalan distribution files are in Xalan-C downloads. The Xerces distribution files are in Xerces-C downloads.
Xalan distribution files  Xerces distribution files  Platform 
Xalan-C_1_4-win32.zip  xerces-c2_1_0-win32.zip  Windows32 
Xalan-C_1_4-linux.tar.gz  xerces-c2_1_0-linux7.2gcc3.1.tar.gz  Redhat Linux 7.2 
Xalan-C_1_4-aix.tar.gz  xerces-c2_1_0-AIX51_5.02.tar.gz  AIX 4.3 
Xalan-C_1_4-solaris.tar.gz  xerces-c2_1_0-.Sol2.7ForCC.tar.gz  Solaris 2.6 
Xalan-C_1_4-hp-ux.tar.gz  xerces-c2_1_0-HP11ACC.tar.gz  HP-UX 11.0 (32 bit) 
Xalan-C_1_4-hp-ux-64.tar.gz  xerces-c2_1_0-HP11ACC_64.tar.gz  HP-UX 11.0 (64 bit) 

The Windows32 distribution was built with MSVC 6.0 SP3 and Dinkumware C++ library fixes. The Red Hat Linux 7.2 32-bit distribution was built with gcc 3.1. The AIX 4.3 32-bit distribution was built with IBM C and C++ for AIX 5.02. The Solaris 2.6 32-bit distribution was built with Sun Workshop 6 update 2. The HP-UX 11 32-bit and 64-bit distributions were built with aCC A.03.33.

NoteUse GNU tar to untar the Solaris distribution file; see A tar checksum error on Solaris .

This release also includes alpha support for building 64-bit Solaris and AIX binaries. See building 64-bit binaries.

If you want to take advantage of the support for number formatting, sorting, and encoding the ICU provides, you should also download and install the International Components for Unicode (ICU); see Using the ICU,


Setting up the path/library path
 
For Windows
 

To use the Windows distribution, you must place the Xalan executables and the Xalan and Xerces libraries on the path:

  • Put xml-xalan\c\Build\Win32\VC6\Release and xerces-c2_1_0-win32\bin on the path.

The Visual C++ Xalan project included with the Windows release knows the relative paths to the Xalan headers and libraries, but it does not know where you have unzipped the Xerces distribution. If you plan to use Visual C++ to build Xalan applications or rebuild Xalan, you must also provide Visual C++ with access to the Xerces headers and libraries.

Use the Visual C++ Tools menu to open the Options dialog box, go to the Directories tab, and do the following:

  • Add the path to xerces-c2_1_0-win32\include to the list of directories of Include files (see the figure below).
  • Add the path to xerces-c2_1_0-win32\lib to the list of directories of Library files (see the figure below).


For UNIX
 

To use one of the UNIX distributions, you must place the Xalan executable on the path, and the Xalan and Xerces libraries on the library path.

For the Xalan-C++ Linux distribution:

  • Put xml-xalan/c/bin on the path (PATH).
  • Put xml-xalan/c/lib and xerces-c2_1_0-linux7.2gcc3.1.tar.gz/lib on the library path (LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.

For the Xalan-C++ AIX distribution:

  • Put xml-xalan/c/bin on the path (PATH).
  • Put xml-xalan/c/lib and xerces-c2_1_0-AIX51_5.02.tar.gz/lib on the library path (LIBPATH), or copy the shared libraries to /usr/lib.

For the Xalan-C++ HP-UX 11 32-bit distribution:

  • Put xml-xalan/c/bin on the path (PATH).

  • Put xml-xalan/c/lib and xerces-c2_1_0-HP11ACC.tar.gz/lib on the library path (SHLIB_PATH), or copy the shared libraries to /usr/lib.

For the Xalan-C++ HP-UX 11 64-bit distribution:

  • Put xml-xalan/c/bin on the path (PATH).

  • Put xml-xalan/c/lib and xerces-c2_1_0-HP11ACC_64.tar.gz/lib on the library path (SHLIB_PATH), or copy the shared libraries to /usr/lib.

For the Xalan-C++ Solaris distribution:

  • Put xml-xalan/c/bin on the path (PATH).

  • Put xml-xalan/c/lib and xerces-c2_1_0-linux7.2gcc3.1.tar.gz/lib on the library path (LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.


Trying out the samples
 

The Xalan-C++ distribution includes a number of basic sample applications. We have precompiled these samples for you so they are ready to run, and you can review the source files to see just how they work.

To run the samples, do the following:

  1. Set up your path (see above). In the Windows32 distribution, the sample executables are in xml-xalan\c\Build\Win32\VC6\Release. In the UNIX distributions, the executables are in xml-xalan/c/bin.
  2. Go to the samples subdirectory containing the sample.
  3. Run the sample from the command line (in Windows, use the DOS shell).
  4. Examine the application source files.

For example, go to the SimpleTransform subdirectory and issue the following command:

SimpleTransform

SimpleTransform uses the foo.xsl stylesheet to transform foo.xml, and writes the transformation result to foo.out. To see how the example works, examine the source files: foo.xml, foo.xsl, foo.out, and SimpleTransform.cpp.

For more information about the samples, see Xalan-C++ Samples.


Performing your own transformations from the command line
 

The Xalan executable lets you perform transformations from the command line. The command line for most standard transformations is as follows:

Xalan -o outputfile xmlSource stylesheet

where xmlSource is the XML source file name, stylesheet is the XSL stylesheet file name, and outputfile is the output file name.

If you want the output to be displayed on the screen, simply omit the -o flag and outputfile.

You can use this utility to try out XSL stylesheets you have written, to make sure they do what you expect with the XML source files they are designed to transform. The utility provides useful messages if the source file or stylesheet is not well formed. If you include a DOCTYPE statement or Schema hint in your XML source files and include the -v flag on the command line, the utility will also let you know whether the XML document is valid (conforms to that DOCTYPE or Schema). For more information, see Command-Line Utility.


Setting up your own XSLT applications
 

You can start by using your own XML source files and XSL stylesheets with the sample applications, which illustrate a number of usage patterns. For more information on setting up applications, see Basic Usage Patterns.



Copyright © 2001 The Apache Software Foundation. All Rights Reserved.