DO NOT REPLY [Bug 23047] New: - [XSLTC] stange behaviour with java extensions in XSLTC

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23047>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23047

[XSLTC] stange behaviour with java extensions in XSLTC

           Summary: [XSLTC] stange behaviour with java extensions in XSLTC
           Product: XalanJ2
           Version: 2.5
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Xalan-Xsltc
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: adam@grummen.net


Using the java extensions, it seems to lose values stored in java objects. For
example, I had code such as this:

<xsl:variable name="v" select="java:java.util.Vector.new()"/>
<xsl:for-each select="//Whatever">
  <xsl:variable name="tmp" select="java:add($v, 'hello')"/>
</xsl:for-each>

This worked fine under xalan interpreted, but xsltc would give me an empty
vector. BUT, if I added another for-each loop around the code, it worked. The
new code:

<xsl:for-each select="/">
  <xsl:variable name="v" select="java:java.util.Vector.new()"/>
  <xsl:for-each select="//Whatever">
    <xsl:variable name="tmp" select="java:add($v, 'hello')"/>
  </xsl:for-each>
</xsl:for-each>