The following issue has been updated:

    Updater: Brian Minchau (mailto:[EMAIL PROTECTED])
       Date: Fri, 24 Sep 2004 7:51 AM
    Changes:
             Component changed to parse or compile
             Component changed to XSLTC
             Component changed from XSLTC parse/compile
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XALANJ-1819?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XALANJ-1819

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XALANJ-1819
    Summary: [XSLTC] bad xsl compilation if exslt used in one xsl
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: XalanJ2
 Components: 
             parse or compile
             XSLTC
   Versions:
             2.5Dx

   Assignee: 
   Reporter: Robert Jacolin

    Created: Thu, 11 Mar 2004 2:57 PM
    Updated: Fri, 24 Sep 2004 7:51 AM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
I compile a list of xsl. Two of them use exslt extension for node-set() function.
If I include all the xsl, a third xsl failed to process (see below). If I
removed the two ones with exslt functions, all xsl work well.

The crash comes with this fragment of xsl :
<xsl:template name="toto">
  <!-- This works -->
  <xsl:variable name="good"/>
  <xsl:variable name="goot-too" select="."/>
  <!-- This failed -->
  <xsl:variable name="titi"></xsl:variable>
  <xsl:variable name="titi">Argh!</xsl:variable>
  ...
</xsl:template>

The exception is :
Exception in thread "main" java.lang.VerifyError: (class: translet/xsl/toto, met
hod: template$dot$270 signature: (Lorg/apache/xalan/xsltc/DOM;Lorg/apache/xml/dt
m/DTMAxisIterator;Lorg/apache/xml/serializer/SerializationHandler;I)V) Incompati
ble object argument for function call
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:140)
        at org.apache.xalan.xsltc.cmdline.Transform.loadTranslet(Transform.java:
136)
        at org.apache.xalan.xsltc.cmdline.Transform.doTransform(Transform.java:1
50)
        at org.apache.xalan.xsltc.cmdline.Transform.main(Transform.java:337)

When I compile without the two xsl which make the problem, the class size is
smaller than when I compile it with all xsl (so there are a lot of bytcode added).

The problem occurs with jdk 1.4.1 and 1.4.2, with xalan 2.5.2 and 2.6.0.

A workaround seems compile the two buggy xsl alone, and all others together.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to