SSDN - inbuilt SAXON does not appesar support saxon ext

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

(Deleted User)

Subject: inbuilt SAXON does not appesar support saxon ext
Author: (Deleted User)
Date: 27 Sep 2002 04:02 AM

Can you help. I have been using saxon as an external processor for some time. However, when I try to use the internal I have problems with the saxon extension functions such as saxon:distinct that does not work.

We are also having problems with errors from the external processor not being shown and I have a colleague who has been unable to get saxon working on NT4 at all.

Thanks for you patience with all these questions.

Minollo I.

Subject: Re: inbuilt SAXON does not appesar support saxon ext
Author: Minollo I.
Date: 27 Sep 2002 10:27 AM

>...
>Can you help. I have been using saxon as an external processor for some
>time. However, when I try to use the internal I have problems with the
>saxon extension functions such as saxon:distinct that does not work.

Martin, what version of Stylus Studio are you running?
Extension functions are supported in the latest build, available from:
http://www.stylusstudio.com/update

>We are also having problems with errors from the external processor not
>being shown

From the built-in Saxon you mean? Or an external (no debugging enabled)
processor? What kind of errors? Can you send me a testcase about this?

>and I have a colleague who has been unable to get saxon working on NT4 at all.

Does she get an error when running Stylus, or is it just Saxon which is not
working?
What are her JVM settings? Can you tell us what information you see in the
Help|About box about the JVM being used?

BTW, Saxon-based debugging is still part of the 4.5 beta program; it's not
in the released product, only in the beta one
(http://www.stylusstudio.com/beta).

Thanks,
Minollo

(Deleted User)

Subject: Re: inbuilt SAXON does not appesar support saxon ext
Author: (Deleted User)
Date: 30 Sep 2002 05:53 AM

Thanks for the reply. My colleagues JVm is currently 1.3.0 - C Classic VM from Sun. How do we update Stylus to use a later version.

As far as Saxon is concerned when I run with the external no debugging attached version it all works(on my machine) but when I run with the prebuilt version on 4.5 beta I now get a simple java.runtime exception and no information. It was complaining that my machines classpath had some dodgy files. This sort of makes me feel that even you 'internal' saxon needs me to set up the CP correctly in the main environment. Is this so? In other words does the 'internal debugging saxon' use my external independent saxon files?

(Deleted User)

Subject: Re: inbuilt SAXON does not appesar support saxon ext
Author: (Deleted User)
Date: 30 Sep 2002 06:02 AM

Below is the full error stack

java.lang.RuntimeException
java.lang.NullPointerException

at com.exln.stylus.CProcessorDriver.trace(CProcessorDriver.java:115)

at com.exln.stylus.CSaxonDriver.enter(CSaxonDriver.java:191)

at com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:597)

at com.icl.saxon.style.LiteralResultElement.process(LiteralResultElement.java:288)

at com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:610)

at com.icl.saxon.style.XSLGeneralVariable.getSelectValue(XSLGeneralVariable.java:238)

at com.icl.saxon.style.XSLVariable.process(XSLVariable.java:89)

at com.icl.saxon.style.XSLStyleSheet.process(XSLStyleSheet.java:623)

at com.icl.saxon.Controller.transformDocument(Controller.java:1075)

at com.icl.saxon.Controller.transform(Controller.java:946)

at com.exln.stylus.CSaxonDriver.doProcessing(CSaxonDriver.java:104)

at com.exln.stylus.CProcessorDriver.process(CProcessorDriver.java:52)

Minollo I.

Subject: Re: inbuilt SAXON does not appesar support saxon ext
Author: Minollo I.
Date: 30 Sep 2002 10:04 AM

Can you send me the XSLT+XML document you are using to reproduce this
problem? Or does it just happen to you with *any* xslt?

Thanks,
Minollo

Ivan Pedruzzi

Subject: RE: inbuilt SAXON does not appesar support saxon ext
Author: Ivan Pedruzzi
Date: 30 Sep 2002 06:48 AM

Robert,

> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager]
> Sent: Monday, September 30, 2002 6:08 AM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: Re: inbuilt SAXON does not appesar support saxon ext
>
>
> From: "Martin Roberts"
>
> Thanks for the reply. My colleagues JVm is currently 1.3.0 -
> C Classic VM from Sun. How do we update Stylus to use a
> later version.

After installing the latest JDK go to Tools -> Options -> Application
Settings then click "Auto detect"

>
> As far as Saxon is concerned when I run with the external no
> debugging attached version it all works(on my machine) but
> when I run with the prebuilt version on 4.5 beta I now get a
> simple java.runtime exception and no information. It was
> complaining that my machines classpath had some dodgy files.

Could you post the exact error message ?

> This sort of makes me feel that even you 'internal' saxon
> needs me to set up the CP correctly in the main environment.
> Is this so? In other words does the 'internal debugging
> saxon' use my external independent saxon files?

The System ClassPath should not affect the "embedded" Saxon in any way.

Ivan

>
>
>
> To reply: mailto:stylus-studio-tech.5687@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
>

(Deleted User)

Subject: Re: inbuilt SAXON does not appesar support saxon ext
Author: (Deleted User)
Date: 02 Oct 2002 07:41 AM

Your latest build seems to fix the inbuilt saxon problems.

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

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 to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

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.