XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
(Deleted User) 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:

xmlns:Ext="class:com.hg.client"
exclude-result-prefixes="Ext"
>

and the declaration further into 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

Postnext
(Deleted User) Subject: JAVA extension exception in v 3.0.0 b47
Author: (Deleted User)
Date: 07 Aug 2001 05:20 AM
Whoah, it seems that your webboard ate my less than and greater than symbols...not good for discussions on XML ehh?

Anyway, the invocation of the java extension looks like this:

xsl:value-of select='Ext:HG_cl_XSLServices.lookupStationCode($cc,$zip)'

Bart

Postnext
Minollo I.Subject: Re: JAVA extension exception in v 3.0.0 b47
Author: Minollo I.
Date: 07 Aug 2001 09:00 AM

>...
>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:
select='Ext:lookupStattionCode($cc,$zip)'

Both Xalan and Stylus will understand it.

Hope this helps,
Minollo

Postnext
(Deleted User) 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:

>select='Ext:lookupStattionCode
>($cc,$zip)'

Both Xalan and
>Stylus will understand
>it.

Hope this helps,
Minollo



Posttop
Minollo I.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?

Thanks,
Minollo

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.