lp:~gagern/xalan/trunk

Created by Martin von Gagern and last modified

bzr-svn import of upstream svn trunk.

This is an unmodified import of http://svn.apache.org/repos/asf/xalan/java/trunk created using the bzr-svn plugin.

Get this branch:
bzr branch lp:~gagern/xalan/trunk
Only Martin von Gagern can upload to this branch. If you are Martin von Gagern please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Martin von Gagern
Project:
Xalan
Status:
Development

Recent revisions

4471. By zongaro

Part of fix for Jira issue XALANJ-2446:

The implementation of Parser.getQName(String,String,String) method was ensuring
that any particular pair of namespace URI and local part of the name would
result in a unique QName object. It did not take into account the prefix,
despite the fact that the original prefix might be associated with a different
namespace URI in this new context or no namespace at all.

Fixed this by making getQName take into account all three of the namespace URI,
local part of the name and prefix in order to create unique QName objects.

Some other parts of XSLTC depended on the assumption that a QName object
uniquely identified a pair consisting of the namespace URI and local part of
the name and used object reference comparisons (== or !=) on QName objects.
These comparisons all had to change to use equals(Object) for comparison
instead. The implementation of QName.equals(Object) itself had to change to
consider the namespace URI and local part of the name rather than relying on
object identity.

Part of fix for Jira issue XALANJ-2447:

The handling of exclude-result-prefixes for an xsl:stylesheet had the complete
set of excluded prefixes accumulated on the xsl:stylesheet for the main
stylesheet module. However, the scope of the attribute is supposed to consist
only of elements that are direct descendants of an element that has the
attribute, and does not extend to imported or included stylesheets. The same
is true of namespaces excluded because they have been declared as extension
element prefixes.

Fixed this by maintaining a stack of excluded prefixes that's pushed on entry
to the Stylesheet.parseOwnChildren method and popped on exit from the same.
The push operation clears the current set of excluded prefixes and the pop
operation restores the set of excluded prefixes that were in effect for the
importing or including stylesheet.

Reviewed by Christine Li (jycli () ca ! ibm ! com)

4470. By zongaro

Part of fix for Jira issue XALANJ-2447.

The handling of exclude-result-prefixes for an xsl:stylesheet had the complete
set of excluded prefixes accumulated on the xsl:stylesheet for the main
stylesheet module. However, the scope of the attribute is supposed to consist
only of elements that are direct descendants of an element that has the
attribute, and does not extend to imported or included stylesheets. The same
is true of namespaces excluded because they have been declared as extension
element prefixes.

Fixed this by maintaining a stack of excluded prefixes that's pushed on entry
to the Stylesheet.parseOwnChildren method and popped on exit from the same.
The push operation clears the current set of excluded prefixes and the pop
operation restores the set of excluded prefixes that were in effect for the
importing or including stylesheet.

Reviewed by Christine Li (jycli () ca ! ibm ! com)

4469. By zongaro

Part of fix for Jira issue XALANJ-2446:

The implementation of getQName(String,String,String) method was ensuring
that any particular pair of namespace URI and local part of the name would
result in a unique QName object. It did not take into account the prefix,
despite the fact that the original prefix might be associated with a different
namespace URI in this new context or with no namespace at all.

Fixed this by making getQName take into account all three of the namespace URI,
local part of the name and prefix in order to create unique QName objects.

Reviewed by Christine Li (jycli () ca ! ibm ! com)

4468. By zongaro

Fix for Jira issue XALANJ-2402.

Unlike all other AST nodes, the AST nodes created for literal result elements,
extension elements and unknown elements did not have a reference to the XSLT
Parser class. This results in an NPE later if the processor needs to access
the Parser instance (or other fields through it, such as the XSLTC instance).

Reviewed by Christine Li (jycli () ca ! ibm ! com)

4467. By minchau

Updating the maintanence version to 1 ( so the product version is now 2.7.1 )

4466. By minchau

Updating the bug list for the website.
It already had XALANJ-2206 in the list, but
we have fixed XALANJ-1243 and XALANJ-2395 recently
so I'm adding them in too.

4465. By minchau

Committing fix for XALANJ-2206
Patch from Vadim Gritsenko.
Patch was modified slightly and approved by Brian Minchau.

The fix lets users set the "enable-inlining" feature specifically
in the case of TemplatesHandler,
where the default value in Stylesheet class was wreaking havoc.

4464. By kcormier

Patch for XALANJ-2395. Reviewed by Brian Minchau.

4463. By zongaro

Added an equals(String) method to the XMLString interface. This allows the
caller to compare an XMLString to a Java String without forcing the XMLString
to be converted to a String.

Part of patch for XALANJ-1243. Reviewed by Brian Minchau (<email address hidden>).

4462. By zongaro

Added an equals(String) method to the XMLString interface. This allows the
caller to compare an XMLString to a Java String without forcing the XMLString
to be converted to a String.

In this particular class (XString), modified equals(XMLString) to take advantage
of the new XMLString.equals(String). If the argument for the comparison
contains a java.lang.String, then comparing that with the String held by this
XString is likely the fastest way to perform the comparison; otherwise, we give
the argument the chance to compare itself natively with the String contained by
this XString.

Part of patch for XALANJ-1243. Reviewed by Brian Minchau (<email address hidden>).

Branch metadata

Branch format:
Branch format 6
Repository format:
Bazaar RepositoryFormatKnitPack6RichRoot (bzr 1.9)
This branch contains Public information 
Everyone can see this information.