What's new in Xalan-Java 2


	What's new in Xalan-Java Version 2.7.0


	Support for JAXP 1.3

Support for JAXP 1.3 has been introduced in this release of Xalan-Java. JAXP 1.3 includes a new javax.xml.xpath package, which provides an object-model neutral API for the evaluation of XPath expressions and access to the evaluation environment. Please refer to Using the JAXP 1.3 XPath API for details on how to use the new XPath API. You can also look at the code in the samples ApplyXPathJAXP , XPathResolver and ExtensionFunctionResolver.

There are also a few new transformer features in JAXP 1.3, as described in the following list:

A new method TransformerFactory.setFeature(String name, boolean value)

A new method Transformer.reset()

A new nextSibling attribute is introduced for DOMResult, accessible by the constructors, getter and setter methods.

Support for the secure processing feature


	New default error handling behavior

The behavior of the default ErrorListener was changed in this release of Xalan-Java, in order to conform with a clarification of the required behavior described by JAXP 1.3. If an application does not register its own ErrorListener, the default ErrorListener is used which reports all warnings and errors to System.err and does not throw any Exceptions. Applications are strongly encouraged to register and use ErrorListeners that insure proper behavior for warnings and errors. The default ErrorListener of the old Xalan-Java Interpretive processor throws exceptions on errors and fatal errors. If your code expects exceptions to be thrown on errors and fatal errors, you have to set a customized ErrorListener on TransformerFactory and/or Transformer. You can use org.apache.xml.utils.DefaultErrorHandler as a sample ErrorListener implementation.


	Support for XML 1.1

This release of Xalan-Java adds support for Namespaces in XML 1.1 and XML 1.1 output documents. The processors:

support C0 control characters

handle C1 control characters in a way that is consistent with the requirements of XML 1.1

treat NEL (U+0085) and LSEP (U+2028) as end-of-line markers

support Internationalized Resource Identifiers (IRIs)

support the additional characters in NCNames and QNames permitted by XML 1.1 and Namespaces in XML 1.1

The processors do not undeclare namespaces other than the default namespace in serialized documents Also, Full normalization is not supported.

An input document can be either XML 1.0 or XML 1.1. Also, a stylesheet document can be either XML 1.0 or XML 1.1. A stylesheet document must conform to the XSLT 1.0 specifications.

Note that it is possible for a stylesheet module that is an XML 1.1 document to use constructs that cannot be serialized as part of a valid XML 1.0 document, and for a stylesheet module that is an XML 1.0 document to use constructs that cannot be serialized as part of a valid XML 1.1 document. For example, a stylesheet module that is an XML 1.1 document might contain a literal result element whose name contains characters that are not permitted as part of a QName in a document that conforms to Namespaces for XML 1.0. The user needs to ensure that the nodes created by the stylesheet can be serialized as part of a well-formed document of the required version of XML.


	Support for Alternative BSF Implementations

Extensions written in Java are directly supported by Xalan-Java. For extensions written in languages other than Java, Xalan-Java uses the Bean Scripting Framework (BSF), an architecture for incorporating scripting into Java applications and applets, and an implementation of BSF must be available on the classpath. In previous releases, IBM's BSF implementation (bsf.jar from 2001) has been included in the Xalan-Java distribution. Some time ago IBM donated their BSF implementation to the Apache Jakarta BSF project. As of this release, the IBM bsf.jar is no longer included in the Xalan-Java distribution. To use extensions written in languages other than Java, please download a version of Jakarta BSF and put it on your classpath. To use a different BSF implementation, please refer to setting the BSFManager.


	New serializer.jar

In this release of Xalan-Java the code related to serialization of output result trees has been pulled out of xalan.jar and moved into a new jar file, named serializer.jar.

The code in serializer.jar has been modified to have no build or runtime dependencies on the rest of the code in Xalan-Java, therefore, serializer.jar can be used in a stand-alone fashion through its public APIs. Although the code has been modified to create a stand-alone jar, the serializer public APIs have not changed and the package names and classnames are the same as they were last release.