Java Extensions cause crash in XSLTC while working fine in Xalan
----------------------------------------------------------------

         Key: XALANJ-2062
         URL: http://issues.apache.org/jira/browse/XALANJ-2062
     Project: XalanJ2
        Type: Bug
  Components: XSLTC  
    Versions: 2.6    
 Environment: Win32, Linux
    Reporter: Holger Rehn


I use XSLTC in my own application running under JBoss (Win32/Linux) and Orion 
(Linux). When using the Java Extensions I get the following error:

FEHLER:  'null'
SCHWER WIEGENDER FEHLER:  'Die Formatvorlage konnte nicht kompiliert werden.'
java.lang.NullPointerException
   at org.apache.xalan.xsltc.compiler.StringCall.translate(StringCall.java:68)
   at 
org.apache.xalan.xsltc.compiler.StringLengthCall.translate(StringLengthCall.java:44)
   at org.apache.xalan.xsltc.compiler.CastExpr.translate(CastExpr.java:231)
   at 
org.apache.xalan.xsltc.compiler.EqualityExpr.translateDesynthesized(EqualityExpr.java:199)
   at org.apache.xalan.xsltc.compiler.If.translate(If.java:99)
   at 
org.apache.xalan.xsltc.compiler.SyntaxTreeNode.translateContents(SyntaxTreeNode.java:490)
   at org.apache.xalan.xsltc.compiler.ForEach.translate(ForEach.java:148)
   at 
org.apache.xalan.xsltc.compiler.SyntaxTreeNode.translateContents(SyntaxTreeNode.java:490)
   at 
org.apache.xalan.xsltc.compiler.LiteralElement.translate(LiteralElement.java:412)
   at 
org.apache.xalan.xsltc.compiler.SyntaxTreeNode.translateContents(SyntaxTreeNode.java:490)
   at 
org.apache.xalan.xsltc.compiler.LiteralElement.translate(LiteralElement.java:412)
   at 
org.apache.xalan.xsltc.compiler.SyntaxTreeNode.translateContents(SyntaxTreeNode.java:490)
   at 
org.apache.xalan.xsltc.compiler.LiteralElement.translate(LiteralElement.java:412)
   at 
org.apache.xalan.xsltc.compiler.SyntaxTreeNode.translateContents(SyntaxTreeNode.java:490)
   at org.apache.xalan.xsltc.compiler.Template.translate(Template.java:335)
   at 
org.apache.xalan.xsltc.compiler.TopLevelElement.compile(TopLevelElement.java:56)
   at org.apache.xalan.xsltc.compiler.Mode.compileNamedTemplate(Mode.java:572)
   at org.apache.xalan.xsltc.compiler.Mode.compileTemplates(Mode.java:589)
   at org.apache.xalan.xsltc.compiler.Mode.compileApplyTemplates(Mode.java:841)
   at 
org.apache.xalan.xsltc.compiler.Stylesheet.compileModes(Stylesheet.java:580)
   at org.apache.xalan.xsltc.compiler.Stylesheet.translate(Stylesheet.java:695)
   at org.apache.xalan.xsltc.compiler.XSLTC.compile(XSLTC.java:335)
   at org.apache.xalan.xsltc.compiler.XSLTC.compile(XSLTC.java:410)
   at 
org.apache.xalan.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:720)

-> the style sheet I'm using stripped down to a minimum <-
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:java="http://xml.apache.org/xslt/java"; version="1.0" 
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
  
  <xsl:param name="connection" />                
  
  <xsl:param name="knrTable" 
select="java:com.sqlgmbh.tcsap.xsl.LookupTable.new( $connection, 
'LA.VERTRAEGE3', 'LA.VERTRAEGE3.PKN' )"/>

  <xsl:template match="/">
    <xsl:if test="string-length(string(java:get($knrTable, '0')))!=0 "/>
  </xsl:template>
  
</xsl:stylesheet>
<-------------------------------------------------------->

If I switch back to Xalan everything works fine.
The error above seems a bit missleading since if I remove the content of my 
template the error changes to:

FEHLER:  'METHOD_NOT_FOUND_ERRcom.sqlgmbh.tcsap.xsl.LookupTable:new'

I really can't see a possibility how this could be possible. The error remains 
even if I include the "missing" class directly in the xalan.jar file.

Just a few more details:
At startup the application loads a number of style sheets compiles them into 
Templates objects and stores them. Every once in a while the application has to 
transform XML data. To do so it loads an appropriate Templates object, 
generates a Transformer object, sets the "connection" param (data base 
connection) and executes the Transformer. This application has worked for years 
now so I guess it's not the problem.

If you need further information please don't hesitate to ask!

-- 
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