Sorry about the inconvenience caused here.
At one level we haven't changed anything - there were already
dependencies on javax.xml.stream classes in 9.2. However, they were in
places where you were more likely to get away with not satisfying them,
for example in XQJ. There's now a reference in net.sf.saxon.Sender,
which is pretty much central to anything you do.
I'm going to see if there's anything we can do about this in the first
9.3 maintenance release. No guarantees, but I'll see what can be done.
We do have JDK 1.5 testing on the pre-release checklist, but it looks as
if those tests must have inadvertently been run on a classpath that
included the free-standing Stax libraries.
On 11/11/2010 14:04, Nigel Whitaker wrote:
> Like Stéphane I've been investigating this Saxon 9.3/Java SE 5 issue for
> a couple of days and considering options for our future releases, eg:
> a) redistribute Saxon 9.2 and postpone our 9.3 plans for the moment
> b) make Java SE 6 a requirement (as Oracle say they finished supporting
> SE 5 a year ago)
> c) saying Java SE 5 is supported with jars downloadable from some 3rd
> party site
> d) redistributing the missing javax.xml.stream classes in some way
> For option c Michael and Stéphane are suggesting the dev.java.net jars:
> Stéphane Vilboux wrote:
>> The file is available here
> And these do have a complex CDDL+GPL+classpath license:
> Le 10/11/2010 14:51, Michael Kay a écrit :
>> Unfortunately the license conditions for these modules don't allow me to
>> redistribute them with Saxon.
> However, I've found that the javax.xml.stream classes are also available
> as part of the Apache XML Commons external
> package which, like the XML Commons resolver, is covered by the Apache
> 2.0 license.
> I've done some minimal testing and they seem to allow Saxon 9.3 to at
> least run in JDK 1.5:
> $ java -version
> java version "1.5.0_23"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_23-b01)
> Java HotSpot(TM) Server VM (build 1.5.0_23-b01, mixed mode)
> $ java -jar /usr/local/java/saxonhe9-3-0-1j/saxon9he.jar
> Exception in thread "main" java.lang.NoClassDefFoundError:
> at net.sf.saxon.Configuration.<init>(Configuration.java:139)
> $ java -cp
> No source file name
> Saxon-HE 188.8.131.52J from Saxonica
> Usage: see http://www.saxonica.com/documentation/using-xsl/commandline.html
> Format: net.sf.saxon.Transform options params
> Options available: -? -a -c -config -cr -dtd -expand -explain -ext -im
> -init -it -l -m -now -o -opt -or -outval -p -r -repeat -s -sa -strip -t
> -T -TJ -TP -traceout -tree -u -val -versionmsg -warnings -x -xi
> -xmlversion -xsd -xsdversion -xsiloc -xsl -xsltversion -y
> We are thinking about redistributing (in our releases) Saxon 9.3 (PE)
> with the xml-apis.jar from Apache commons (or perhaps a 'stripped down'
> jar to only include javax.xml.stream.*).
> I'm still looking at the legal/licensing issues, but are there any
> technical reasons to prefer either jsr173_1.0_api.jar or xml-apis.jar ?