Subject:SaxonB8.4 testing Author:Tony Lavinio Date:25 Apr 2006 08:50 AM
In current versions of Stylus Studio, when you select the
processor as Saxon, there is a button that lets you change
processor-specific properties.
For Saxon, you can choose whether you want to use Saxon-B
or Saxon-SA from that ensuing dialog.
Also, I'd update to a more recent version of Saxon; both
Stylus Studio 2006 Release 2 and Saxonica are now on
Saxon 8.7.1, which is conformant with the current specifications
and is more stable than 8.4.
Subject:SaxonB8.4 testing Author:Jack Tan Date:26 Apr 2006 12:42 PM
I have access to Stylus Studio 6 XML Enterprise Edition Build 377o, (Saxon 8.4) and Stylus Studio XML Enterprise Edition 2006, Release 2, build 591b (Saxon 8.7).
None of them has any visible means of explicit selection of Saxon B or SA. But based on your answer, I am assuming that using Studio 6 will guarantee that I am Saxon B-ready. Thanks, it saves time.
Prior to do any further conversion work, I would like to validate that I do not need any licenses to use the code/components/modules/adapters that come with the generated code. In my case I am accessing a simple XML file and converting it into html - no database access, no legacy data formatting just simple files with text (XML). So for example "StylusFileFactory URIResolver" will come with a .jar that can be included in distribution.
Question: where can I find the required %classpathList% to configure a stand-alone application that I can run outside of Stylus Studio?
This is the first time I am preparing a tool for distribution and most probably these are very elementary questions and concerns but I am just trying to eliminate any potential problems and surprises ;-)
In SS 6, there is no button for setting processor-specific properties.
But in 2006, there is - it's right next to the combobox uses to select
the processor. In 2006, that button leads to an extra dialog that
lets you set all sorts of nifty parameters, including whether or not
you are running Saxon-SA.
See http://www.stylusstudio.com/docs/v2006/d_xquery28.html#wp548299
There is a runtime fee if (and only if) you use our URI resolver to
access wscc:, db: or adapter: filesystems. You should disable the
option "[ ] Use Stylus Studio URI resolver" before testing and
generating your code to make sure of this. If you haven't used any
of those separately-licensed modules, what you generate is just
plain Java code that can be freely used. In that case, you won't
need the StylusFileFactory bits at all, or any of our jar files.
The appropriate classpath is added to the project when you generate
the Java code the first time, but it's entirely possible, if you've
disabled using our URI resolver, that you'll just need saxon8.jar.
If you want to see what it looks like, look at Project|Set Classpath.
One of my co-workers pointed out that if you use the enterprise
edition, we only bundle saxon8sa.jar. If you use professional,
we only bundle saxon8.jar.
Since saxon8sa.jar is a superset of saxon8.jar, you can use it
in B mode as it is - as long as you don't use any schema-aware
features, it acts just like saxon8.jar.
Or purchase a license from Michael Kay and use it in SA mode,
or you can download saxon8.jar - there are instructions on http://www.saxonica.com/