calling java extension

stolte · January 9th, 2008, 04:38 PM

I have built a java extension, but am receiving an error when calling the function.

The XSLT:

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet xmlns:xsl=" http://www.w3.org/1999/XSL/Transform" version="2.0"
      xmlns:parse="java:ParseNodeSet">

      <xsl:template match="/">
            <xsl:variable name="table" select="parse:buildAndParseNodeset(//schedule)"/>

            <html>
                  <head/>
                  <body><xsl:copy-of select="$table"/></body>
            </html>

      </xsl:template>

</xsl:stylesheet>

The error msg:

C:\Users\Deep\Desktop\saxonsa8-9-0-4j>java -jar saxon8.jar template.xml generate
Table.xsl
Error at xsl:variable on line 9 of file:/C:/Users/Deep/Desktop/saxonsa8-9-0-4j/g
enerateTable.xsl:
  XPST0003: XPath syntax error at char 48 on line 9 in {...eNodeset(//ns1:Energy
Schedu...}:
    Cannot find a matching 1-argument function named {java:ParseNodeSet}buildAnd
ParseNodeset()
Failed to compile stylesheet. 1 error detected.

Does anyone have any ideas why saxon is not able to locate the function?

The class and java files are stored within the saxon folder, and the cass has been defined on the classpath.

Any help is greatly appreciated.

mhkay · January 9th, 2008, 04:44 PM

A common mistake - when you use the -jar option to run a Java application, the classpath is ignored, so only the classes in the JAR file are available. You need to use the

java -cp... net.sf.saxon.Transform

approach.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

stolte · January 9th, 2008, 04:50 PM

Forgive me I am new to calling java extensions, how would I call that from the command line? I tried

>java net.sf.saxon.Transform file.xml file.xsl

but received the same message

samjudson · January 10th, 2008, 09:04 AM

java net.sf.saxon.Transform -s:source -xsl:stylesheet -o:output

http://www.saxonica.com/documentatio...mmandline.html

/- Sam Judson : Wrox Technical Editor -/

mhkay · January 10th, 2008, 01:03 PM

Possible reasons for failing to find a class are that the class isn't on the classpath (OK, you say it is, but we've all been wrong on this); that the class isn't public; that the method isn't public; that the method isn't static.

Using the -TJ option on the command line will produce diagnostics that may help you to distinguish these possible causes.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference