Hello,
Our company is currently using Xalan 2.6. However, we have found that  there
is a memory leak in the XMLReaderManager class, when the XMLReader instances
are not properly removed after the thread finishes and is garbage collected.
This issue has been known and is now fixed in Xalan 2.7.0. Therefore, we are
now analyzing whether it is suitable for us to migrate to Xalan 2.7.0. The
problem that arrises is that we do not know if there are any backward
compatibility issues between 2.7.0 and 2.6. After spending some time reading
the release notes I have found the following changes that might affect the
migration (confirm with Yes  / No if these are important changes )

1.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 ...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.
 -* Assuming that we do what is described here, is there any other parts of
the code Xalan code affected by this behaviour ? *

2. 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.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.
*- From what I understand, there are no consequences besides adding and
additional .jar file to the build path. Is that correct ?

*3. Are there any additional major changes from 2.6 to 2.7.0 that need to be
addressed?

4. *Is there a list, containing all the bug-fixes with the appropriate
method / class signature and attribute changes? I saw the history.html file
- is this the complete list?*


Thank you in advance.

Warm Regards,
Dragomir Stanchev

Reply via email to