Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: trunk
Commits on Dec 12, 2009
  1. Committing patch for Jira bug XALANJ-2473 submitted by Martin von Gag…

    Henry Zongaro authored
    …ern.
    
    Corrects the implementation of the DOM Level 3 Node.getTextContent() method
    which was return null for element nodes, rather than the string values of all
    the text node descendants in document order.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@889881 13f79535-47bb-0310-9956-ffa450edef68
Commits on Nov 26, 2009
  1. Applying patch for bug XALANJ-2495 from Martin von Gagern which corre…

    Henry Zongaro authored
    …cts a
    
    mistranslation of two messages to German.  I don't speak or read German, so I'm
    taking it on faith that the new message text improves upon the old.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@884640 13f79535-47bb-0310-9956-ffa450edef68
Commits on Nov 25, 2009
  1. Applying patch contributed by Martin von Gagern for XALANJ-2493 and X…

    Henry Zongaro authored
    …ALANJ-2424.
    
    Quoting from Martin, "The current implementation of nodeList2Iterator is
    broken, because it can not deal with attribute nodes. It relies on copyNodes
    which in turn tries to add attribute nodes as children of some top level node.
    Attributes don't live on the children axis, though, so this is against DOM and
    causes a DOM exception in the Xerces DOM implementation and probably most other
    implementations. The resulting HIERARCHY_REQUEST_ERR was noted e.g. in
    XALANJ-2424.  Furthermore, the implementation is inefficient, because it
    manually copies each and every node from the source document to a new DTM to
    some new DTM....
    
    I dropped copyNodes in favor of Document.importNode, to avoid code duplication
    and rely on supposedly more heavily tested code. I also added another level of
    elements, so that there is one such dummy node for every item of the source
    list, with always a single child or element. A few assertions help ensure this
    single child policy. This is especially important in the new implementation,
    because otherwise it would become difficult to get the proxied nodes and the
    newly DTMified nodes into correct order.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@884287 13f79535-47bb-0310-9956-ffa450edef68
Commits on Jun 19, 2008
  1. Part of fix for Jira issue XALANJ-2446:

    Henry Zongaro authored
    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)
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@669374 13f79535-47bb-0310-9956-ffa450edef68
  2. Part of fix for Jira issue XALANJ-2447.

    Henry Zongaro authored
    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)
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@669373 13f79535-47bb-0310-9956-ffa450edef68
  3. Part of fix for Jira issue XALANJ-2446:

    Henry Zongaro authored
    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)
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@669372 13f79535-47bb-0310-9956-ffa450edef68
Commits on Oct 12, 2007
  1. Fix for Jira issue XALANJ-2402.

    Henry Zongaro authored
    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)
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@584164 13f79535-47bb-0310-9956-ffa450edef68
Commits on Sep 20, 2007
  1. Updating the maintanence version to 1 ( so the product version is now…

    Brian James Minchau authored
    … 2.7.1 )
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@577939 13f79535-47bb-0310-9956-ffa450edef68
  2. Updating the bug list for the website.

    Brian James Minchau authored
    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.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@577937 13f79535-47bb-0310-9956-ffa450edef68
  3. Committing fix for XALANJ-2206

    Brian James Minchau authored
    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.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@577935 13f79535-47bb-0310-9956-ffa450edef68
Commits on Sep 14, 2007
  1. Patch for XALANJ-2395. Reviewed by Brian Minchau.

    Kevin Cormier authored
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@575747 13f79535-47bb-0310-9956-ffa450edef68
Commits on Aug 27, 2007
  1. Added an equals(String) method to the XMLString interface. This allow…

    Henry Zongaro authored
    …s 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 (minchau@ca.ibm.com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@570109 13f79535-47bb-0310-9956-ffa450edef68
  2. Added an equals(String) method to the XMLString interface. This allow…

    Henry Zongaro authored
    …s 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 (minchau@ca.ibm.com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@570108 13f79535-47bb-0310-9956-ffa450edef68
Commits on Aug 7, 2007
  1. Updating the date for Xalan-J 2.7.1 release and

    Brian James Minchau authored
    including more fixed bugs in the list for the release:
    1434
    2108
    2339
    2375
    2377
    2384
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@563700 13f79535-47bb-0310-9956-ffa450edef68
  2. Committing changes for XALANJ-2358 on behalf of Brian Minchau (in ord…

    Kevin Cormier authored
    …er to test that my committer SVN account is working). The changes were reviewed by Henry Zongaro.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@563659 13f79535-47bb-0310-9956-ffa450edef68
  3. Committing changes for XALANJ-2358 on behalf of Brian Minchau (in ord…

    Kevin Cormier authored
    …er to test that my committer SVN account is working). The changes were reviewed by Henry Zongaro.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@563656 13f79535-47bb-0310-9956-ffa450edef68
Commits on Jun 8, 2007
  1. Fix for XALANJ-2384.

    Henry Zongaro authored
    The code generated for the topLevel and transform methods of a translet was
    generated using DTM.ROOT_NODE (i.e., zero) as the value of the root node for
    the initial context.  However, that is not a valid node handle.
    
    The proper way of getting the handle of root of the initial input document is
    through DOM.getIterator().next().
    
    Patch was reviewed by Christine Li (jycli () ca ! ibm ! com)
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@545471 13f79535-47bb-0310-9956-ffa450edef68
Commits on Apr 13, 2007
  1. Patch for XALANJ-2377

    Henry Zongaro authored
    VariableBase.removeReference was effectively being used to decrement a reference
    counter for local variables.
    
    At one time, XSLTC used to release JVM stack slots as soon as the last
    reference to a local variable occurred, but that resulted in a bug if loops
    were involved.  So the code was changed to release a local variable slot only
    when the containing construct went out of scope - this was done with a call to
    VariableBase.unmapRegister from SytaxTreeNode.translateContents.
    
    However, VariableBase.unmapRegister still contained a vestige of the old
    reference counting code - it was checking whether any references to the variable
    still existed.  In the presence of "Closures," the number of calls to
    VariableBase.addReference did not equal the number of calls to
    VariableBase.removeReference (for no good reason), so the variable was not
    marked by VariableBase.unmapRegister as going out of scope.  This caused later
    problems for outlining in org.apache.xalan.xsltc.compiler.util.MethodGenerator.
    
    The fix is to remove VariableBase.removeReference, since XSLTC should no longer
    on that to determine whether it can release a variable slot.  The
    VariableBase.addReference method remains, however, because XSLTC uses that to
    determine whether a variable can be discarded completely.
    
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@528589 13f79535-47bb-0310-9956-ffa450edef68
Commits on Apr 2, 2007
  1. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    In the case of JAXPVariableStack, which extends VariableStack, the default
    constructor can always use specify the minimal stack size on the super class's
    constructor.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524815 13f79535-47bb-0310-9956-ffa450edef68
  2. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    Also added two new XPathContext constructors which accept a boolean argument
    that indicates whether the context for variables needs to be push/popable.
    When it's false, the XPathContext will create a minimally-sized VariableStack.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524814 13f79535-47bb-0310-9956-ffa450edef68
  3. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    Also added two new XPathContext constructors which accept a boolean argument
    that indicates whether the context for variables needs to be push/popable.
    When it's false, the XPathContext will create a minimally-sized VariableStack.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524813 13f79535-47bb-0310-9956-ffa450edef68
  4. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    In the case of JAXPVariableStack, which extends VariableStack, the default
    constructor can always use specify the minimal stack size on the super class's
    constructor.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524812 13f79535-47bb-0310-9956-ffa450edef68
  5. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    Also added two new XPathContext constructors which accept a boolean argument
    that indicates whether the context for variables needs to be push/popable.
    When it's false, the XPathContext will create a minimally-sized VariableStack.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524811 13f79535-47bb-0310-9956-ffa450edef68
  6. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Lexer.tokenize was always creating an OpMapVector object with large initial
    sizes.  This was wasteful, because each XPath expression so tokenize might
    need only a small amount of space.  Instead, changed the initial size to be
    equal to five times the length of the string to be tokenized, just as a
    very conservative estimate.  This has a significant impact on the performance
    of the XPath API.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524810 13f79535-47bb-0310-9956-ffa450edef68
  7. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    Also added two new XPathContext constructors which accept a boolean argument
    that indicates whether the context for variables needs to be push/popable.
    When it's false, the XPathContext will create a minimally-sized VariableStack.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524809 13f79535-47bb-0310-9956-ffa450edef68
  8. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    Also added two new XPathContext constructors which accept a boolean argument
    that indicates whether the context for variables needs to be push/popable.
    When it's false, the XPathContext will create a minimally-sized VariableStack.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524808 13f79535-47bb-0310-9956-ffa450edef68
  9. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Added a new constructor and corresponding reset method that allow the caller
    to specify the initial size for the arrays contained in a VariableStack.  This
    is important for XPath expression evaluation, where additional stack entries
    are never needed.  Previously, the arrays were always allocated based on the
    maximum recursion depth permitted by the XSLT processor, which was caused
    unnecessary initialization overhead using the various XPath APIs.
    
    Also added two new XPathContext constructors which accept a boolean argument
    that indicates whether the context for variables needs to be push/popable.
    When it's false, the XPathContext will create a minimally-sized VariableStack.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524807 13f79535-47bb-0310-9956-ffa450edef68
  10. Part of fix for Jira issue XALANJ-2375.

    Henry Zongaro authored
    Changed default constructor to defer creating a PrintWriter through which to
    report any error messages until a message actually needs to be reported.  A
    PrintWriter instance consumes a substantial amount of space, and deferring its
    creation saves initialization time for the XPath API and XSLT.
    
    Reviewed by Christine Li (jycli () ca ! ibm ! com).
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@524806 13f79535-47bb-0310-9956-ffa450edef68
Commits on Mar 1, 2007
  1. Fix for JIRA issue XalanJ-1434

    Brian James Minchau authored
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@513117 13f79535-47bb-0310-9956-ffa450edef68
Commits on Feb 9, 2007
  1. Applying patch for XALANJ-2339 from Kevin Cormier (kcormier () ca ! i…

    Henry Zongaro authored
    …bm ! com).
    
    Code for converting the Object reference for parameter to a node-set
    (DTMAxisIterator) was simply performing a clone of the iterator.  However,
    cloning an iterator also clones its iteration state, so that if the original
    iterator was part way through its iteration for some reason, the cloned
    iterator would not return all the nodes in the node set.  The fix is to reset
    the cloned iterator prior to returning it.
    
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@505310 13f79535-47bb-0310-9956-ffa450edef68
Commits on Dec 21, 2006
  1. Website updates for the release notes and some other

    Brian James Minchau authored
    clean up applied to TRUNK.
    
    Patch2 from JIRA issue XALANJ-2359 is applied.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@489426 13f79535-47bb-0310-9956-ffa450edef68
  2. Website updates for the release notes and some other

    Brian James Minchau authored
    clean up applied to TRUNK.
    
    Patch2 from JIRA issue XALANJ-2359 is applied.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@489425 13f79535-47bb-0310-9956-ffa450edef68
Commits on Dec 13, 2006
  1. Applying documentation patch to remove references to

    Brian James Minchau authored
    gump on the builds and downloads pages.
    
    Patch applied from XALANJ-2356
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@486788 13f79535-47bb-0310-9956-ffa450edef68
  2. Pulling out the patch that was from XALANJ-2133 since it caused

    Brian James Minchau authored
    regressions in some of the flavours of testing.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@486494 13f79535-47bb-0310-9956-ffa450edef68
Commits on Nov 24, 2006
  1. upgraded for XALANJ-2345 for the Xalan-J 2.7.1 release.

    Brian James Minchau authored
    Changed Xerces version to 2.9.0 and year to 2006.
    
    git-svn-id: https://svn.apache.org/repos/asf/xalan/java/trunk@478770 13f79535-47bb-0310-9956-ffa450edef68
Something went wrong with that request. Please try again.