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

Release notes for Xalan-C++ version 1.2

Status
 
Changes since Xalan-C++ version 1.1
 

Major updates since version 1.1 include:


Bug reporting
 

All known Xalan-C++ bugs are listed in Bugzilla (the Apache bug database). For a list of open bugs with links to each bug report, see XalanC open bugs. If you find a new bug, please enter a XalanC bug report in this database.

NoteBefore you can enter your first bug report, you must submit your email address to Bugzilla and receive a password.

We strongly encourage you write patches for problems you find and submit them to xalan-dev@xml.apache.org. We review the patches we receive to make sure they do not break something else, and (assuming they do not) include them in our next release. In the interest of fixing bugs, adding enhancements, and addressing outstanding design issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.


Version of Xerces-C++ to use
 

Xalan-C++ version 1.2 has been tested with Xerces-C++ version 1.5.1. Each Xalan-C++ version 1.2 download includes the Xerces-C++ distribution for the specified platform. For information about including The Xerces-C++ libraries on the path, see Setting up the system path.

Important You may experience unpredictable anomalies if your Xalan and Xerces builds are not in synch. If you download an update to Xalan, check the release notes to determine which version of Xerces you should use.


To-do tasks for future Xalan-C++ releases
 
  • Add support for extension elements

  • Fix any conformance bugs we or our users find

  • Expand the XalanTransformer simplified API.

Watch the Xalan Development Mailing List for more information and for ideas about how you can get involved.



Build Notes
 
Rebuilding Xalan-C++
 

If you want to rebuild Xalan-C++, you need the following:

  • The Xalan-C++ source files
  • The Xerces-C++ header and (for Windows) .lib files
  • (Optional) The ICU header and (for Windows) .lib files

The Xalan-C++ source files and The required Xerces-C++ files are in the distribution.

For information on using the International Components for Unicode (ICU), see Using the ICU.

NoteIf you are not rebuilding with the ICU, you do not need the ICU header or .lib files.

To rebuild the Windows32 release, use the Microsoft Visual C++ 6.0 project files. To rebuild the Linux or AIX release, use the make file in the root of the source directory. The builds look for Xerces-C++ and ICU in directories parallel to the xml-xalan directory.


Layout
 

Important We have set up the Visual C++ projects and the UNIX make files to look for Xerces in the directory structure replicated in our distribution files (see Xalan-C++ Distributions). This matches the structure that results from downloading xml-xerces/c from the Apache XML CVS repository and building with the Visual C++ project files or the UNIX make file.

If you are using a Xerces-C++ binary distribution that you have obtained independently from this Xalan-C++ distribution, you must either modify the Xalan-C++ project files or makefile, or rearrange the build directory structure as indicated in the following illustration.

For UNIX, the XERCESROOT environment variable points to the Xerces-C root directory. For Windows, the Xerces-C root directory must be named xml-xerces, and it must be at the same level as the Xalan-C++ root directory. For all environments, the ICU root directory must be named icu, and it must be at the same level as the Xalan-C++ root directory.

ICU layout for Xalan-C++ build
 


NoteKeep in mind that at any given point in time the Xalan-C++ and Xerces-C++ source trees in the Apache XML repository may not be consistent. When we release a version of Xalan-C++ we certify that it is compatible with a given version of Xerces-C++. To be safe, stick with distributions that we certify to be compatible. Reminder: Xalan-C++ version 1.2 is compatible with the Xerces-C++ that is included with the distribution..

Xalan-C++ version 1.2 has been tested with International Components for Unicode(ICU) 1.8.1 source files. You may be able to use newer ICU releases as they appear.

Steps for doing a Windows build
 

To build Xalan-C++ on Windows, you need Xerces-C++ and MS Visual C++ 6.0 installed with Service Pack 3 for Visual C++ and Visual Studio. You should also apply the bug fixes for the C++ standard library that shipped with Visual C++ 6.0. These fixes are available from the Dinkumware site: http://www.dinkumware.com/vc_fixes.html.

  1. (Optional) If you are rebuilding the ICUBridge, install the ICU so the icu root directory is at the same level as the xml-xerces root directory (see Using the ICU.

    If you want TestXSLT to use ICU support for number formatting and sorting, install the ICU, uncomment the #define XALAN_USE_ICU statement in process.cpp, and use the Visual C++ Project Dependencies command to add ICUBridge to the list of TestXSLT dependencies (see Enabling ICU support for TestXSLT).

  2. Use Visual C++ to open the Xalan workspace from the xml-xalan\c\Projects\Win32\VC6.

  3. Use Visual C++ to rebuild everything or specific dynamic link libraries and executables of interest.


Steps for doing a UNIX build
 
  1. Set the XERCESCROOT environment variable to the root of xml-xerces.

  2. Set the XALANCROOT environment variable to the complete path to the root of the Xalan-C++ distribution.

  3. AIX and Solaris only: Download STLport and set the STLPORTROOT environment variable to the complete path to the STLPort distribution.
    (This step is not required for Linux or HP-UX 11 because The Linux GNU compiler and HP aCC compiler include the STL (Standard Template Library.)

  4. (Optional) If you are including the ICUBridge, install the ICU (see Using the ICU) and use the shell to define XALAN_USE_ICU.

    If you are using Bourne Shell, K Shell, or Bash:
         export XALAN_USE_ICU "1"

    If you are using C Shell:
         setenv XALAN_USE_ICU="1"

  5. Change directory to xml-xalan/c/src in the Xalan-C++ distribution.

  6. Use the chmod +x command to set the executable flags for conf* and runConfigure.

         chmod +x runConfigure
         chmod +x conf*

  7. Run the runConfigure utility with at least the platform flag (Linux) or the platform, C compilier, and C++ compiler flags (AIX) as indicated below.

    Linux:  runConfigure -p linux
    AIX:    runConfigure -p aix -c xlc -x xlC

    HP-UX 11:  runConfigure -p hp-11 -c cc -x aCC

    Solaris:  runConfigure -p solaris -c cc -x CC

    To see the other runConfigure flags you may include, use the help flag:

         runConfigure -h

  8. Purge the previous build:

         make clean

  9. Run the new build:

         make
    or
         make targ

    where targ is ommitted or is all (rebuild all), lib (the XSLT libary), or testXSLT (the testSXSLT executable). ICUBridge is included in the build of TestXSLT if XALAN_USE_ICU is defined.

NoteThe command you use for setting environment variables depends on the shell you are using.
For Bourne Shell, K Shell, or Bash use export ENVAR="val"
For C Shell, use setenv ENVAR "val"
where ENVAR is the environment variable name and val is the environment variable setting. You can check the setting of an environment variable with echo $ENVAR

Rebuilding a sample application
 

The Windows32 distribution includes a Visual C++ workspace for the sample applications. This workspace is in the samples directory. If you modify a sample and want to recompile it, you can recompile the .cpp file(s) and rebuild the executable.

The make files that come with the UNIX distributions include targets for rebuilding one or all of the sample applications (with the exception of the ThreadSafe sample, which in its current form only runs under Windows). To rebuild one or more sample applications, go to the xml-xalan/c/src directory and run

     make targ

where targ is Samples (all the samples), XalanTransform, SimpleTransform, StreamTransform, UseStylesheetParam, TraceListen, CompileStylesheet, (Windows only) ThreadSafe XPathWrapper, ExternalFunctions,or ApacheModuleXSLT.

NoteFor information on building Apache Module, see ApacheModuleXSLT


Getting in Touch
 

Your feedback is more than welcome. Offers of help are even more so! Perhaps you would like to contribute to the ongoing development, testing, or documentation of Xalan-C++.

Please email your comments, questions, suggestions, bug reports, and offers to help to Xalan Development Mailing List.


Cumulative history of software changes
 
Changes for Xalan-C++ version 1.1
 

In addition to adding to the list of platforms on which Xalan-C++ builds, our focus for this release has been on bug fixes, performance enhancements, and providing a simplified C++ and C API for performing standard transformations. Major updates since version 1.0 include:

  • Added HP-UX 11 build.

  • Added Solaris build.

  • Greatly improved performance.

  • Improved conformance to the XSLT specification.

  • Simplified the C++ API and provided a C API for performing standard transformations with the XalanTransformer class and associated header files.

  • Added sample illustrating use of XalanTransformer and the new C++ API: XalanTransform.

  • Added sample illustrating use of XalanTransformer, the new C API, and how to run Xalan-C++ and perform transformations on an Apache Web server: ApacheModuleXSLT.

  • Added the StreamTransform sample.

  • Eliminated dependencies on non-public Xerces headers; accordingly can now build with the Xerces distribution.

  • Fixed namespace mapping and inheritance problems.

  • Fixed failure of <copy-of ...> to include CRLFs (if any) in the result.

  • Fixed bug sorting in reverse document order based on position.

  • Fixed <xsl:number> bug with use of letter-value="traditional" for "classical" Greek numbering.

  • Fixed use of <xsl:fallback> within a top-level extension function.

  • Fixed HTML output method bug. The <HEAD> element was not including a <META> tag with the encoding.

  • Fixed bug using key() in match patterns to find descendants.

  • Fixed bug using the id() function in complex match patterns.

  • Fixed problem outputting multiple single-character CDATA sections.

  • Fixed problem outputting whitespace characters.

  • Fixed problem transforming from a stream on UNIX platforms.

  • Fixed a bug with the document() function, which was generating a syntax error if called in the following manner: document(string,/).

  • Fixed named templates bug accepting global parameter when called with a parameter of the same name that the named template does not recognize.

Changes for Xalan-C++ version 1.0
 

Major updates since version 0.40.0 include:

  • Full support for namespace handling

  • Full implementation of the format-number() function and support for the decimal-format element

  • Integration with the International Components for Unicode (ICU) for number formatting, sorting, and output encoding

  • Support for the exclude-result-prefixes attribute

  • Support for the output encoding attribute

Changes for Xalan-C++ version 0.40.0
 

Major updates since version 0.30.0 include:

  • Permitting OS file names (as well as URLs) as command-line arguments with TestXSLT

  • Stricter compliance for HTML and XML output

  • Improved handling of relative URI's

  • Improved handling of Import and Include

  • Better namespace handling (although there are still problems here)

  • Support for Document() function

  • Support for XPath predicates

  • Better handling of parameters to stylesheet and templates

  • Full implementation of axes ( with the exception of namespace:: )




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