Subject:JAVA extension exception in v 3.0.0 b47 Author:(Deleted User) Date:07 Aug 2001 05:18 AM
All,
I would like to use the interactive debugging of Stylus with JAVA extensions, but it seems that Stylus can't handle anything but really simple extensions. I am then forced to switch to an external processor on the options/processor tab.
I have a pretty straight forward JAVA extension that uses the Xalan extension mechanism. I have all the necessary CLASSPATH information setup prior to launching Stylus and yet the built-in parser can't handle this extension.
This works fine in Xalan-J v 2.1.0 outside of Stylus or when I set Stylus to use an external processor.
It has two parts, the definition at the top of the XSL:
The exception I get is: Class not found 'com.hg.client' (however this is just my package name.
Questions:
1. Does Stylus internal processor utilize the same extension declaration syntax as Xalan or is it compatible?
2. Will it ever be compatible?
3. Am I forced to use the external processor option for all future XSLs that need to use JAVA extensions?
TIA
Bart Jenkins, CTO
Globeflow SA
bjenkins@globeflow.com
Subject:Re: JAVA extension exception in v 3.0.0 b47 Author:(Deleted User) Date:08 Aug 2001 12:23 PM
Carlo,
Tried your suggested change, Xalan still likes it but Stylus still does not see it: I get a "java.lang.NoSuchMethodError".
One thing: This class is inside a JAR file and not a stand-alone class file. Could that be the problem?
Bart Jenkins
bjenkins@globeflow.com
On 8/7/01 9:00:57 AM, Carlo Innocenti wrote:
>
>...
>Questions:
>1. Does
>Stylus internal processor
>utilize the same extension
>declaration
>syntax as Xalan
>or is it compatible?
The
>syntax recognized by the
>internal Stylus processor is
>also recognized
by Xalan; the
>vice-versa is not always true,
>as in the case you
>mention.
>2. Will it ever be
>compatible?
As soon as this
>becomes a standard, with XSLT
>2.0
>3. Am I forced to use
>the external processor option
>for all future XSLs
>that
>need to use JAVA
>extensions?
No; in your case,
>you can define:
>xmlns:Ext="com.hg.client.HG_cl
>_XSLServices"
and invoke it
>as:
Subject:Re: JAVA extension exception in v 3.0.0 b47 Author:Minollo I. Date:08 Aug 2001 12:26 PM
> Tried your suggested change, Xalan still likes it but Stylus still does
> not see it: I get a "java.lang.NoSuchMethodError".
>
>One thing: This class is inside a JAR file and not a stand-alone class
>file. Could that be the problem?
I don't think so.
Can you send us a testcase we can use to see what's going on?