Hello community, here is the log from the commit of package saxon for openSUSE:Factory checked in at 2012-06-26 17:37:13 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/saxon (Old) and /work/SRC/openSUSE:Factory/.saxon.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "saxon", Maintainer is "[email protected]" Changes: -------- --- /work/SRC/openSUSE:Factory/saxon/saxon.changes 2011-09-23 12:45:21.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.saxon.new/saxon.changes 2012-06-26 17:37:15.000000000 +0200 @@ -1,0 +2,22 @@ +Thu Jun 21 08:11:35 UTC 2012 - [email protected] + +- license update: MPL-1.0 and Apache-2.0 + Compatible with Fedora declaration + +------------------------------------------------------------------- +Fri May 18 07:30:20 UTC 2012 - [email protected] + +- update to 9.3.0.4 - needed by updated xmlbeans + * An installation wizard is provided on .NET + * Support for XML Schema 1.1 is almost complete. + * Support for streamed processing of XSLT is greatly extended, making transformation of very large documents much more feasible. + * For the first time, Saxon has support for parallel processing of XSLT to take advantage of multi-core CPUs. + * Many features from the draft 3.0 specifications are implemented. + * The range of data-types available is extended by the provision of immutable maps. + +------------------------------------------------------------------- +Tue Dec 13 13:17:07 UTC 2011 - [email protected] + +- fix license to be in spdx.org format + +------------------------------------------------------------------- Old: ---- saxon-cmdlinefix.patch saxon6-5-5.zip New: ---- saxon-he-9.3.0.4.pom saxon-resources9-3.zip saxon.saxonq.script saxon9-3-0-4source.zip saxonq.1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ saxon.spec ++++++ --- /var/tmp/diff_new_pack.gShUJa/_old 2012-06-26 17:37:18.000000000 +0200 +++ /var/tmp/diff_new_pack.gShUJa/_new 2012-06-26 17:37:18.000000000 +0200 @@ -1,7 +1,7 @@ # -# spec file for package saxon (Version 6.5.5) +# spec file for package saxon # -# Copyright (c) 2009 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -16,48 +16,53 @@ # -%define gcj_support %{?_with_gcj_support:1}%{!?_with_gcj_support:%{?_without_gcj_support:0}%{!?_without_gcj_support:%{?_gcj_support:%{_gcj_support}}%{!?_gcj_support:0}}} -%define section free -%define resolverdir %{_sysconfdir}/java/resolver Summary: The SAXON XSLT Processor from Michael Kay - -Name: saxon -Version: 6.5.5 -Release: 108 -License: MPL .. +License: MPL-1.0 and Apache-2.0 Group: Productivity/Publishing/XML +# net.sf.saxon.om.XMLChar is from ASL-licensed Xerces +Name: saxon +Version: 9.3.0.4 +Release: 0 Url: http://saxon.sourceforge.net/ -Source0: http://download.sf.net/saxon/saxon6-5-5.zip +Source0: https://downloads.sourceforge.net/project/saxon/Saxon-HE/9.3/saxon9-3-0-4source.zip Source1: %{name}.saxon.script -Source2: %{name}.build.script -Source3: %{name}.1 -Patch2: %{name}-cmdlinefix.patch -BuildRequires: jpackage-utils >= 1.6 -BuildRequires: xml-commons-apis -BuildRequires: jdom >= 1.0 -BuildRequires: fop >= 0.20.1 -%if ! %defined suse_version -BuildRequires: java-javadoc -BuildRequires: jdom-javadoc >= 1.0 -BuildRequires: fop-javadoc -%else +Source2: %{name}.saxonq.script +Source3: %{name}.build.script +Source4: %{name}.1 +Source5: %{name}q.1 +Source6: https://downloads.sourceforge.net/project/saxon/Saxon-HE/9.3/saxon-resources9-3.zip +Source7: http://irrational.googlecode.com/svn/trunk/maven-repo/net/sf/saxon/saxon-he/9.3.0.4/saxon-he-9.3.0.4.pom +BuildRoot: %{_tmppath}/%{name}-%{version}-build +BuildArch: noarch + +BuildRequires: ant +BuildRequires: bea-stax-api +BuildRequires: dom4j BuildRequires: java-devel +BuildRequires: jdom BuildRequires: unzip -BuildRequires: ant -%endif -Requires: jaxp_parser_impl -Requires: /usr/sbin/update-alternatives -Provides: jaxp_transform_impl -%if ! %{gcj_support} -BuildArch: noarch -%endif -BuildRoot: %{_tmppath}/%{name}-%{version}-build -%if %{gcj_support} -BuildRequires: gnu-crypto -BuildRequires: java-gcj-compat-devel -Requires(post): java-gcj-compat -Requires(postun): java-gcj-compat -%endif +BuildRequires: xml-commons-apis +BuildRequires: xom + +BuildRequires: java-javadoc +#BuildRequires: jdom-javadoc >= 1.0 +#BuildRequires: fop-javadoc + +Requires: bea-stax +Requires: bea-stax-api +Provides: jaxp_transform_impl = %{version}-%{release} + +# Older versions were split into multile packages +Obsoletes: %{name}-dom < %{version}-%{release} +Provides: %{name}-dom = %{version}-%{release} +Obsoletes: %{name}-jdom < %{version}-%{release} +Provides: %{name}-jdom = %{version}-%{release} +Obsoletes: %{name}-sql < %{version}-%{release} +Provides: %{name}-sql = %{version}-%{release} +Obsoletes: %{name}-xom < %{version}-%{release} +Provides: %{name}-xom = %{version}-%{release} +Obsoletes: %{name}-xpath < %{version}-%{release} +Provides: %{name}-xpath = %{version}-%{release} %description The SAXON package is a collection of tools for processing XML @@ -84,62 +89,21 @@ So you can use SAXON by writing XSLT stylesheets, by writing Java applications, or by any combination of the two. - - -Authors: --------- - Michael H. Kay <[email protected]> - -%package aelfred -License: MPL .. -Summary: Java XML parser -Group: Productivity/Publishing/XML -#Provides: jaxp_parser_impl -#Requires: /usr/sbin/update-alternatives -Requires: xml-commons-apis - -%description aelfred -A slightly improved version of the AElfred Java XML parser from -Microstar. - - - -Authors: --------- - Michael H. Kay <[email protected]> - %package manual -License: MPL .. Summary: Manual for saxon Group: Productivity/Publishing/XML %description manual Manual for saxon. - - -Authors: --------- - Michael H. Kay <[email protected]> - %package javadoc -License: MPL .. Summary: Javadoc for saxon Group: Productivity/Publishing/XML -Requires(post): /bin/rm,/bin/ln -Requires(postun): /bin/rm %description javadoc Javadoc for saxon. - - -Authors: --------- - Michael H. Kay <[email protected]> - %package demo -License: MPL .. Summary: Demos for saxon Group: Productivity/Publishing/XML Requires: %{name} = %{version}-%{release} @@ -147,109 +111,80 @@ %description demo Demonstrations and samples for saxon. - - -Authors: --------- - Michael H. Kay <[email protected]> - -%package fop -License: MPL .. -Summary: FOP support for saxon -Group: Productivity/Publishing/XML -Requires: %{name} = %{version}-%{release} -Requires: fop >= 0.20.1 - -%description fop -FOP support for saxon. - - - -Authors: --------- - Michael H. Kay <[email protected]> - -%package jdom -License: MPL .. -Summary: JDOM support for saxon -Group: Productivity/Publishing/XML -Requires: %{name} = %{version}-%{release} -Requires: jdom >= 1.0 - -%description jdom -JDOM support for saxon. - - - -Authors: --------- - Michael H. Kay <[email protected]> - %package scripts -License: MPL .. Summary: Utility scripts for saxon Group: Productivity/Publishing/XML -Requires: jpackage-utils >= 1.6 Requires: %{name} = %{version}-%{release} +Requires: jpackage-utils >= 1.6 %description scripts Utility scripts for saxon. - -Authors: --------- - Michael H. Kay <[email protected]> - %prep %setup -q -c -unzip -q source.zip -cp -p %{SOURCE2} ./build.xml -%patch2 -p0 + +unzip -q %{SOURCE6} +cp -p %{SOURCE3} ./build.xml + +# deadNET +rm -rf net/sf/saxon/dotnet + +# Depends on XQJ (javax.xml.xquery) +rm -rf net/sf/saxon/xqj + +# This requires a EE edition feature (com.saxonica.xsltextn) +rm -rf net/sf/saxon/option/sql/SQLElementFactory.java + # cleanup unnecessary stuff we'll build ourselves -rm -rf *.jar docs/api +rm -rf docs/api +find . \( -name "*.jar" -name "*.pyc" \) -delete %build -export CLASSPATH=%(build-classpath xml-commons-apis fop jdom) +mkdir -p build/classes +cat >build/classes/edition.properties <<EOF +config=net.sf.saxon.Configuration +platform=net.sf.saxon.java.JavaPlatform +EOF + +export CLASSPATH=%(build-classpath xml-commons-apis jdom xom bea-stax-api dom4j) ant \ -Dj2se.javadoc=%{_javadocdir}/java \ - -Dfop.javadoc=%{_javadocdir}/fop \ - -Djdom.javadoc=%{_javadocdir}/jdom \ - -Dant.build.javac.source=1.4 -Dant.build.javac.target=1.4 + -Djdom.javadoc=%{_javadocdir}/jdom %install -rm -rf $RPM_BUILD_ROOT + # jars mkdir -p $RPM_BUILD_ROOT%{_javadir} -cp -p build/lib/%{name}.jar $RPM_BUILD_ROOT%{_javadir}/%{name}-%{version}.jar -cp -p build/lib/%{name}-aelfred.jar $RPM_BUILD_ROOT%{_javadir}/%{name}-aelfred-%{version}.jar -cp -p build/lib/%{name}-fop.jar $RPM_BUILD_ROOT%{_javadir}/%{name}-fop-%{version}.jar -cp -p build/lib/%{name}-jdom.jar $RPM_BUILD_ROOT%{_javadir}/%{name}-jdom-%{version}.jar -(cd $RPM_BUILD_ROOT%{_javadir} && for jar in *-%{version}*; do ln -sf ${jar} `echo $jar| sed "s|-%{version}||g"`; done) +cp -p build/lib/%{name}.jar $RPM_BUILD_ROOT%{_javadir}/%{name}.jar + # javadoc -mkdir -p $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version} -cp -pr build/api/* $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version} -ln -s %{name}-%{version} $RPM_BUILD_ROOT%{_javadocdir}/%{name} +mkdir -p $RPM_BUILD_ROOT%{_javadocdir}/%{name} +cp -pr build/api/* $RPM_BUILD_ROOT%{_javadocdir}/%{name} + # demo mkdir -p $RPM_BUILD_ROOT%{_datadir}/%{name} cp -pr samples/* $RPM_BUILD_ROOT%{_datadir}/%{name} + # scripts mkdir -p $RPM_BUILD_ROOT%{_bindir} -sed 's,__RESOLVERDIR__,%{resolverdir},' < %{SOURCE1} \ - > $RPM_BUILD_ROOT%{_bindir}/%{name} +install -p -m755 %{SOURCE1} $RPM_BUILD_ROOT%{_bindir}/%{name} +install -p -m755 %{SOURCE2} $RPM_BUILD_ROOT%{_bindir}/%{name}q mkdir -p $RPM_BUILD_ROOT%{_mandir}/man1 -sed 's,__RESOLVERDIR__,%{resolverdir},' < %{SOURCE3} \ - > $RPM_BUILD_ROOT%{_mandir}/man1/%{name}.1 +install -p -m644 %{SOURCE4} $RPM_BUILD_ROOT%{_mandir}/man1/%{name}.1 +install -p -m644 %{SOURCE5} $RPM_BUILD_ROOT%{_mandir}/man1/%{name}q.1 + # jaxp_transform_impl ghost symlink ln -s %{_sysconfdir}/alternatives \ $RPM_BUILD_ROOT%{_javadir}/jaxp_transform_impl.jar -# jaxp_parser_impl ghost symlink -#ln -s %{_sysconfdir}/alternatives \ -# $RPM_BUILD_ROOT%{_javadir}/jaxp_parser_impl.jar -%if %{gcj_support} -export CLASSPATH=$(build-classpath gnu-crypto) -%{_bindir}/aot-compile-rpm -%endif + +# a simple POM +install -dm 755 $RPM_BUILD_ROOT%{_mavenpomdir} +install -m 644 %{SOURCE7} $RPM_BUILD_ROOT%{_mavenpomdir}/JPP-%{name}.pom +sed -i -e 's/saxon-he/saxon/' $RPM_BUILD_ROOT%{_mavenpomdir}/JPP-%{name}.pom +#FIXME: some strange python exception even with javapackages-tools 0.3.1 +# % add_maven_depmap JPP-%{name}.pom %{name}.jar +%add_to_maven_depmap JPP-%{name}.pom %{name}.jar %clean rm -rf $RPM_BUILD_ROOT @@ -257,115 +192,24 @@ %post update-alternatives --install %{_javadir}/jaxp_transform_impl.jar \ jaxp_transform_impl %{_javadir}/%{name}.jar 25 -%if %{gcj_support} -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif -%if %{gcj_support} - -%postun -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif %preun { [ $1 -eq 0 ] || exit 0 update-alternatives --remove jaxp_transform_impl %{_javadir}/%{name}.jar } >/dev/null 2>&1 || : -%if %{gcj_support} -%post aelfred -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif -%if %{gcj_support} - -%postun aelfred -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif -%if %{gcj_support} - -%post fop -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif -%if %{gcj_support} - -%postun fop -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif -%if %{gcj_support} - -%post jdom -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif -%if %{gcj_support} - -%postun jdom -if [ -x %{_bindir}/rebuild-gcj-db ] -then - %{_bindir}/rebuild-gcj-db -fi -%endif - -%post javadoc -rm -f %{_javadocdir}/%{name} -ln -s %{name}-%{version} %{_javadocdir}/%{name} - -%postun javadoc -if [ "$1" = "0" ]; then - rm -f %{_javadocdir}/%{name} -fi +%pre javadoc +# workaround for rpm bug +[ $1 -gt 1 ] && [ -L %{_javadocdir}/%{name} ] && \ +rm -rf $(readlink -f %{_javadocdir}/%{name}) %{_javadocdir}/%{name} || : %files %defattr(0644,root,root,0755) %{_javadir}/%{name}.jar -%{_javadir}/%{name}-%{version}.jar +%{_mavenpomdir}/JPP-%{name}.pom +%{_mavendepmapfragdir}/%{name} %ghost %{_javadir}/jaxp_transform_impl.jar -%if %{gcj_support} -%dir %attr(-,root,root) %{_libdir}/gcj/%{name} -%attr(-,root,root) %{_libdir}/gcj/%{name}/%{name}-%{version}.jar.* -%endif - -%files aelfred -%defattr(0644,root,root,0755) -%{_javadir}/%{name}-aelfred* -#%ghost %{_javadir}/jaxp_parser_impl.jar -%if %{gcj_support} -%attr(-,root,root) %{_libdir}/gcj/%{name}/%{name}-aelfred-%{version}.jar.* -%endif - -%files fop -%defattr(0644,root,root,0755) -%{_javadir}/%{name}-fop* -%if %{gcj_support} -%attr(-,root,root) %{_libdir}/gcj/%{name}/%{name}-fop-%{version}.jar.* -%endif - -%files jdom -%defattr(0644,root,root,0755) -%{_javadir}/%{name}-jdom* -%if %{gcj_support} -%attr(-,root,root) %{_libdir}/gcj/%{name}/%{name}-jdom-%{version}.jar.* -%endif %files manual %defattr(0644,root,root,0755) @@ -373,8 +217,7 @@ %files javadoc %defattr(0644,root,root,0755) -%ghost %doc %{_javadocdir}/%{name} -%doc %{_javadocdir}/%{name}-%{version} +%doc %{_javadocdir}/%{name} %files demo %defattr(0644,root,root,0755) @@ -383,6 +226,8 @@ %files scripts %defattr(0755,root,root,0755) %{_bindir}/%{name} +%{_bindir}/%{name}q %attr(0644,root,root) %{_mandir}/man1/%{name}.1* +%attr(0644,root,root) %{_mandir}/man1/%{name}q.1* %changelog ++++++ saxon.1 ++++++ --- /var/tmp/diff_new_pack.gShUJa/_old 2012-06-26 17:37:18.000000000 +0200 +++ /var/tmp/diff_new_pack.gShUJa/_new 2012-06-26 17:37:18.000000000 +0200 @@ -1,135 +1,148 @@ .\" Kudos to: xsltproc(1), help2man, -.\" http://saxon.sourceforge.net/saxon6.5.3/instant.html -.TH SAXON "1" "July 2004" "6.5.3" "User Commands" +.\" http://www.saxonica.com/documentation/using-xsl/commandline.html +.TH SAXON8 "1" "March 2006" "8.7" "User Commands" .SH NAME -saxon \- Process XML documents with XSLT stylesheets +saxon8 \- manual page for saxon8 .SH SYNOPSIS -.B saxon -\fR[\fIoptions\fR] \fIsource-doc \fR[\fIstyle-doc\fR] [{param=value}\fR...] +.B saxon8 +[\fIoptions\fR] \fIsource-document stylesheet \fR[ \fIparams\fR...] .SH DESCRIPTION -saxon is a command line tool for applying XSLT stylesheets to XML -documents. -.PP -It is invoked from the command line with some options, followed by the -name of the source document to be transformed, followed by the the -name of the stylesheet to use for the transformation, and finally -followed by optional XSL parameters. -.PP -A parameter takes the form name=value, name being the name of the -parameter, and value the value of the parameter. These parameters are -accessible within the stylesheet as normal variables, using the $name -syntax, provided they are declared using a top-level xsl:param -element. If there is no such declaration, the supplied parameter value -is silently ignored. You can specify a parameter value containing -spaces by enclosing it in double quotes, for example name="John Brown". +saxon8 applies a given stylesheet to a given source XML document. + .SH OPTIONS + +For a schema\-aware transformation, specify the option \fB\-sa\fR, or (on the Java platform only) use the alternate entry point com.saxonica.Transform. For more details see Schema\-Aware Transformations. +.TP +The options must come first, then the two file names, then the params. The stylesheet is omitted if the \fB\-a\fR option is present. +.TP +The options are as follows (in any order): .TP \fB\-a\fR -Use the xml-stylesheet processing instruction in the source document -to identify the stylesheet to be used. When using this option, the -style-doc argument should be omitted. -.SP -The <?xml-stylesheet?> processing instruction must have a -pseudo-attribute href that identifies the relative or absolute URL of -the stylesheet document, and a pseudo-attribute type whose value is -"text/xml", "application/xml", or "text/xsl". For example: - - <?xml-stylesheet type="text/xsl" href="../style3.xsl"?> - -Stylesheets embedded within the source document are not -supported in this release. +Use the xml\-stylesheet processing instruction in the source document to identify the stylesheet to be used. The stylesheet argument should be omitted. +.TP +\fB\-c\fR +Indicates that the stylesheet argument identifies a compiled stylesheet rather than an XML source stylesheet. The stylesheet must have been previously compiled as described in Compiling a Stylesheet. +.TP +\fB\-cr\fR classname +Use the specified CollectionURIResolver to process collection URIs passed to the collection() function. The CollectionURIResolver is a user\-defined class that implements the net.sf.saxon.CollectionURIResolver interface. +.TP +\fB\-ds\fR | \fB\-dt\fR +Selects the implementation of the internal tree model. \fB\-dt\fR selects the tiny tree model (the default). \fB\-ds\fR selects the linked tree model. See Choosing a tree model. +.TP +\fB\-im\fR modename +Selects the initial mode for the transformation. If this is namespaced, it can be written as {uri}localname .TP -\fB\-d\fR\fImodel\fR -Selects the implementation of the internal tree model. -dt selects the -"tinytree" model. -ds selects the traditional tree model. The default -is -dt. +\fB\-it\fR template +Selects the initial named template to be executed. If this is namespaced, it can be written as {uri}localname. When this option is used, the source file should be omitted. .TP \fB\-l\fR -Switches line numbering on for the source document. Line numbers are -accessible through the extension function saxon:line-number(), or from -a trace listener. -.TP -\fB\-m\fR \fIclassname\fR -Use the specified Emitter to process the output from xsl:message. The -class must implement the com.icl.saxon.output.Emitter class. This -interface is similar to a SAX ContentHandler, it takes a stream of -events to generate output. In general the content of a message is an -XML fragment. By default the standard XML emitter is used, configured -to write to the standard error stream, and to include no XML -declaration. Each message is output as a new document. +Switches line numbering on for the source document. Line numbers are accessible through the extension function saxon:line\-number(), or from a trace listener. +.TP +\fB\-m\fR classname +Use the specified Emitter to process the output from xsl:message. The class must implement the net.sf.saxon.output.Emitter class. This interface is similar to a SAX ContentHandler, it takes a stream of events to generate output. In general the content of a message is an XML fragment. By default the standard XML emitter is used, configured to write to the standard error stream, and to include no XML declaration. Each message is output as a new document. .TP \fB\-noext\fR -Suppress calls on extension functions, other than system-supplied -Saxon and EXSLT extension functions. This option is useful when -loading an untrusted stylesheet, perhaps from a remote site using an -HTTP URL; it ensures that the stylesheet cannot call Java -methods and thereby gain privileged access to resources on your -machine. -.TP -\fB\-o\fR \fIfilename\fR -Send output to named file. In the absence of this option, output goes -to standard output. The file extension of the output file is used to -decide the default output method if none is specified. -.TP -\fB\-r\fR \fIclassname\fR -Use the specified URIResolver to process all URIs. The URIResolver is -a user-defined class, that extends the com.icl.saxon.URIResolver -class, whose function is to take a URI supplied as a string, and -return a SAX InputSource. It is invoked to process URIs used in the -document() function, in the xsl:include and xsl:import elements, and -(if -u is also specified) to process the URIs of the source file and -stylesheet file provided on the command line. If xml-commons-resolver -is available, defaults to org.apache.xml.resolver.tools.CatalogResolver. +Suppress calls on extension functions, other than system\-supplied Saxon and EXSLT extension functions. This option is useful when loading an untrusted stylesheet, perhaps from a remote site using an http:// URL; it ensures that the stylesheet cannot call Java methods and thereby gain privileged access to resources on your machine. +.TP +\fB\-novw\fR +No version warnings. This suppresses the warning message that is normally issued (as required by the W3C specification) when running an XSLT 2.0 processor against a stylesheet that specifies version=1.0. +.TP +\fB\-o\fR filename +Send output to named file. In the absence of this option, the results go to standard output. If the source argument identifies a directory, this option is mandatory and must also identify a directory; on completion it will contain one output file for each file in the source directory. If the stylesheet writes secondary output files using the xsl:result\-document instruction; this filename acts as the base URI for the href attribute of this instruction. In the absence of this option, secondary output files are written relative to the current working directory. +.TP +\fB\-p\fR +Use the PTreeURIResolver. This option is available in Saxon\-SA only. It cannot be used in conjunction with the \fB\-r\fR option, and it automatically switches on the \fB\-u\fR and \fB\-sa\fR options. The effect is twofold. Firstly, Saxon\-specific file extensions are recognized in URIs (including the URI of the source document on the command line). Currently the only Saxon\-specific file extension is .ptree, which indicates that the source document is supplied in the form of a Saxon PTree. This is a binary representation of an XML document, designed for speed of loading. Secondly, Saxon\-specific query parameters are recognized in a URI. Currently the only query parameter that is recognized is val. This may take the values strict, lax, or strip. For example, source.xml?val=strict loads a document with strict schema validation. +.TP +\fB\-r\fR classname +Use the specified URIResolver to process all URIs. The URIResolver is a user\-defined class, that extends the net.sf.saxon.URIResolver class, whose function is to take a URI supplied as a string, and return a SAX InputSource. It is invoked to process URIs used in the document() function, in the xsl:include and xsl:import elements, and (if \fB\-u\fR is also specified) to process the URIs of the source file and stylesheet file provided on the command line. +.TP +\fB\-sa\fR +Invoke a schema\-aware transformation. Requires Saxon\-SA to be installed. +.TP +\fB\-sall\fR +Strips all whitespace text nodes from source documents before any further processing, regardless of any xsl:strip\-space declarations in the stylesheet, or any xml:space attributes in the source document. +.TP +\fB\-signorable\fR +Strips all ignorable whitespace text nodes from source documents before any further processing, regardless of any xsl:strip\-space declarations in the stylesheet, or any xml:space attributes in the source document. Whitespace text nodes are ignorable if they appear in elements defined in the DTD or schema as having element\-only content. +.TP +\fB\-snone\fR +Strips no whitespace before further processing. (However, whitespace will still be stripped if this is specified in the stylesheet using xsl:strip\-space). .TP \fB\-t\fR -Display version and timing information to the standard error output. +Display version and timing information to the standard error output. The output also traces the files that are read and writing, and extension modules that are loaded. .TP \fB\-T\fR -Display stylesheet tracing information to the standard error -output. Also switches line numbering on for the source document. +Display stylesheet tracing information to the standard error output. This traces execution of each instruction in the stylesheet, so the output can be quite voluminous. Also switches line numbering on for the source document. +.TP +\fB\-TJ\fR +Switches on tracing of the binding of calls to external Java methods. This is useful when analyzing why Saxon fails to find a Java method to match an extension function call in the stylesheet, or why it chooses one method over another when several are available. .TP -\fB\-TL\fR \fIclassname\fR -Run the stylesheet using the specified TraceListener. The classname -names a user-defined class, which must implement -com.icl.saxon.trace.TraceListener. +\fB\-TL\fR classname +Run the stylesheet using the specified TraceListener. The classname names a user\-defined class, which must implement net.sf.saxon.trace.TraceListener +.TP +\fB\-TP\fR +Run the stylesheet using the TraceListener TimedTraceListener. This creates an output file giving timings for each instruction executed. This output file can subsequently be analyzed to give an execution time profile for the stylesheet. See Performance Analysis. .TP \fB\-u\fR -Indicates that the names of the source document and the style document -are URLs; otherwise they are taken as filenames, unless they start -with "http:" or "file:", in which case they are taken as URLs. -.TP -\fB\-w\fR\fIlevel\fR -Indicates the policy for handling recoverable errors in the -stylesheet: -w0 means recover silently, -w1 means recover after -writing a warning message to the system error output, -w2 means signal -the error and do not attempt recovery. (Note, this does not currently -apply to all errors that the XSLT recommendation describes as -recoverable). The default is -w1. -.TP -\fB\-x\fR \fIclassname\fR -Use the specified SAX parser for source file and for any files loaded -using the document() function. The parser must be the fully-qualified -class name of a Java class that implements the org.xml.sax.Parser or -org.xml.sax.XMLReader interface. If xml-commons-resolver is available, -defaults to org.apache.xml.resolver.tools.ResolvingXMLReader. -.TP -\fB\-y\fR \fIclassname\fR -Use the specified SAX parser for all stylesheet files, including any -loaded using xsl:include or xsl:import. The parser must be the -fully-qualified class name of a Java class that implements the -org.xml.sax.Parser or org.xml.sax.XMLReader interface. If -xml-commons-resolver is available, defaults to -org.apache.xml.resolver.tools.ResolvingXMLReader. +Indicates that the names of the source document and the style document are URLs; otherwise they are taken as filenames, unless they start with http: or file:, in which case they are taken as URLs +.TP +\fB\-v\fR +Requests DTD\-based validation of the source file and of any files read using the document() function. Requires an XML parser that supports validation. +.TP +\fB\-val\fR +Requests schema\-based validation of the source file and of any files read using the document() function. This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. +.TP +\fB\-vlax\fR +This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. It requests lax validation of source documents using an XML Schema. That is, the document will be validated if a suitable schema is available, and will not be validated otherwise. +.TP +\fB\-vw\fR +Indicates that validation errors found when validating the result tree should be treated as warnings only. This option is available only with the Saxon\-SA version of the command, com.saxonica.Transform. +.TP +\fB\-w0\fR, w1, or w2 +Indicates the policy for handling recoverable errors in the stylesheet: w0 means recover silently, w1 means recover after writing a warning message to the system error output, w2 means signal the error and do not attempt recovery. (Note, this does not currently apply to all errors that the XSLT recommendation describes as recoverable). The default is w1. +.TP +\fB\-x\fR classname +Use specified SAX parser for source file and any files loaded using the document() function. The parser must be the fully\-qualified class name of a Java class that implements the org.xml.sax.Parser or org.xml.sax.XMLReader interface +.TP +\fB\-y\fR classname +Use specified SAX parser for stylesheet file, including any loaded using xsl:include or xsl:import. The parser must be the fully\-qualified class name of a Java class that implements the org.xml.sax.Parser or org.xml.sax.XMLReader interface +.TP +\fB\-1\fR.1 +Allow XML 1.1 and XML Namespaces 1.1 constructs. This option must be set if source documents using XML 1.1 are to be read, or if result documents are to be serialized as XML 1.1. This option also enables use of XML 1.1 constructs within the stylesheet itself. +.TP +\-? +Display command syntax +.TP +source\-document +Identifies the source file or directory. Mandatory. If this is a directory, all the files in the directory will be processed individually. In this case the \fB\-o\fR option is mandatory, and must also identify a directory, to contain the corresponding output files. A directory must be specified as a filename, not as a URL. The source\-document can be specified as \- to take the source from standard input. +.TP +stylesheet +Identifies the stylesheet. Mandatory unless the \fB\-a\fR option is used. If the \fB\-c\fR option is used, this argument identifies a compiled stylesheet. The stylesheet argument can be specified as \- to read the stylesheet from standard input. + +A param takes the form name=value, name being the name of the parameter, and value the value of the parameter. These parameters are accessible within the stylesheet as normal variables, using the syntax, provided they are declared using a top\-level xsl:param element. If there is no such declaration, the supplied parameter value is silently ignored. If the xsl:param element has an as attribute indicating the required type, then the string value supplied on the command line is cast to this type: this may result in an error, for example if an integer is required and the supplied value cannot be converted to an integer. +.TP +A param preceded by a leading exclamation mark (!) is interpreted as an output parameter. For example, !indent=yes requests indented output. This is equivalent to specifying the attribute indent=yes on an xsl:output declaration in the stylesheet. An output parameter specified on the command line overrides one specified within the stylesheet. +.TP +A param preceded by a leading plus sign (+) is interpreted as a filename or directory. The content of the file is parsed as XML, and the resulting document node is passed to the stylesheet as the value of the parameter. If the parameter value is a directory, then all the immediately contained files are parsed as XML, and the resulting sequence of document nodes is passed as the value of the parameter. For example, +lookup=lookup.xml sets the value of the stylesheet parameter lookup to the document node at the root of the tree representing the parsed contents of the file lookup.xml. +.TP +Under Windows, and some other operating systems, it is possible to supply a value containing spaces by enclosing it in double quotes, for example name=John Smith. This is a feature of the operating system shell, not something Saxon does, so it may not work the same way under every operating system. (In the jEdit console plugin it has to be written as name=John Smith) +.TP +If the parameter name is in a non\-null namespace, the parameter can be given a value using the syntax {uri}localname=value. Here uri is the namespace URI of the parameter's name, and localname is the local part of the name. +.TP +This applies also to output parameters. For example, you can set the indentation level to 4 by using the parameter !{http://saxon.sf.net/}indent\-spaces=4. See also Additional attributes for xsl:output. +.TP +If the \fB\-a\fR option is used, the name of the stylesheet is omitted. The source document must contain a <?xml\-stylesheet?> processing instruction before the first element start tag; this processing instruction must have a pseudo\-attribute href that identifies the relative or absolute URL of the stylsheet document, and a pseudo\-attribute type whose value is text/xml, application/xml, or text/xsl. For example: +.TP +<?xml\-stylesheet type=text/xsl href=../style3.xsl ?> .TP -\fB\-?\fR -Display command syntax. +It is also possible to refer to a stylesheet embedded within the source document, provided it has an id attribute and the id attribute is declared in the DTD as being of type ID. .SH FILES -.B __RESOLVERDIR__/CatalogManager.properties +.B /etc/java/resolver/CatalogManager.properties .RS The central catalog manager configuration file used by \fBsaxon\fR for resolving XML entities and URIs if xml-commons-resolver is available. .SH "SEE ALSO" .BR xsltproc (1) -.SH AUTHOR +.SH AUTHOR Michael H. Kay <[email protected]> ++++++ saxon.build.script ++++++ --- /var/tmp/diff_new_pack.gShUJa/_old 2012-06-26 17:37:18.000000000 +0200 +++ /var/tmp/diff_new_pack.gShUJa/_new 2012-06-26 17:37:18.000000000 +0200 @@ -24,7 +24,7 @@ <mkdir dir="${build.lib}"/> <mkdir dir="${build.doc}"/> <copy todir="${src}"> - <fileset dir="." includes="com/**,org/**"/> + <fileset dir="." includes="com/**,org/**,net/**"/> </copy> </target> @@ -36,34 +36,16 @@ <!-- Build classes --> <target name="classes" depends="prepare"> - <javac srcdir="${src}" destdir="${build.classes}"/> + <javac srcdir="${src}" destdir="${build.classes}" encoding="ISO-8859-1"/> </target> <!-- Build jar archives --> + <target name="jar" depends="classes"> - <!-- aelfred --> - <jar destfile="${build.lib}/${name}-aelfred.jar" - basedir="${build.classes}" - includes="com/icl/saxon/aelfred/*"> - <metainf dir="META-INF" - includes="services/javax.xml.parsers.*" /> - </jar> - <!-- fop --> - <jar destfile="${build.lib}/${name}-fop.jar" - basedir="${build.classes}" - includes="com/icl/saxon/fop/*"/> - <!-- jdom --> - <jar destfile="${build.lib}/${name}-jdom.jar" - basedir="${build.classes}" - includes="com/icl/saxon/jdom/*"/> - <!-- main --> <jar jarfile="${build.lib}/${name}.jar" - basedir="${build.classes}" - excludes="com/icl/saxon/fop/,com/icl/saxon/jdom/,com/icl/saxon/aelfred/"> - <metainf dir="META-INF" - includes="services/javax.xml.transform.*" /> + basedir="${build.classes}"> <manifest> - <attribute name="Main-Class" value="com.icl.saxon.StyleSheet" /> + <attribute name="Main-Class" value="net.sf.saxon.Transform" /> </manifest> </jar> </target> @@ -77,7 +59,8 @@ package="true" author="true" version="true" - packagenames="com.icl.saxon.*,org.w3c.xsl.*" + packagenames="net.sf.saxon.*,org.w3c.xsl.*" + encoding="ISO-8859-1" > <link href="${j2se.javadoc}"/> <link href="${jdom.javadoc}"/> ++++++ saxon.saxon.script ++++++ --- /var/tmp/diff_new_pack.gShUJa/_old 2012-06-26 17:37:18.000000000 +0200 +++ /var/tmp/diff_new_pack.gShUJa/_new 2012-06-26 17:37:18.000000000 +0200 @@ -5,19 +5,19 @@ . /usr/share/java-utils/java-functions -MAIN_CLASS=com.icl.saxon.StyleSheet +MAIN_CLASS=net.sf.saxon.Transform -BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar" +BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar bea-stax-api.jar bea-stax-ri.jar" # Optional jars -CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon saxon-fop \ +CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon \ avalon-logkit xml-commons-resolver 2>/dev/null) || : # If we have resolver, add the CatalogManager.properties dir to CLASSPATH, # and tweak command line options so that it's used. args= if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 ; then - CLASSPATH="$CLASSPATH:__RESOLVERDIR__" + CLASSPATH="$CLASSPATH:/etc/java/resolver" # Tune options to use resolver. r=org.apache.xml.resolver.tools.ResolvingXMLReader for opt in -x -y ; do ++++++ saxon.saxonq.script ++++++ #!/bin/sh # # saxon script # JPackage Project <http://www.jpackage.org/> . /usr/share/java-utils/java-functions MAIN_CLASS=net.sf.saxon.Query BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar bea-stax-api.jar bea-stax-ri.jar" # Optional jars CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon \ avalon-logkit xml-commons-resolver 2>/dev/null) || : # If we have resolver, add the CatalogManager.properties dir to CLASSPATH, # and tweak command line options so that it's used. args= if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 ; then CLASSPATH="$CLASSPATH:/etc/java/resolver" # Tune options to use resolver. r=org.apache.xml.resolver.tools.ResolvingXMLReader for opt in -x -y ; do if ! echo $@ | grep "\\$opt " >/dev/null 2>&1 ; then args="$args $opt $r" fi done r=org.apache.xml.resolver.tools.CatalogResolver if ! echo $@ | grep "\\-r " >/dev/null 2>&1 ; then args="$args -r $r" fi fi # Set parameters set_jvm set_classpath $BASE_JARS set_flags $BASE_FLAGS set_options $BASE_OPTIONS # Let's start run $args "$@" ++++++ saxonq.1 ++++++ .\" Kudos to: xsltproc(1), help2man, .\" http://www.saxonica.com/documentation/using-xquery/commandline.html .TH SAXON8Q "1" "March 2006" "8.7" "User Commands" .SH NAME saxon8q \- manual page for saxon8q .SH SYNOPSIS .B saxon8q [\fIoptions\fR] \fIquery \fR[ \fIparams\fR...] .SH DESCRIPTION saxon8q runs a query contained in a file. .SH OPTIONS The options must come first, then the file name containing the query, then the params. .TP The options are as follows (in any order): .TP \fB\-cr\fR classname Use the specified CollectionURIResolver to process collection URIs passed to the collection() function. The CollectionURIResolver is a user\-defined class that implements the net.sf.saxon.CollectionURIResolver interface. .TP \fB\-ds\fR Use the linked tree model for source documents. See Choosing a Tree Model. .TP \fB\-dt\fR Use the tinytree tree model for source documents. This is the default tree model. See Choosing a Tree Model. .TP \fB\-e\fR Display a query execution plan. This is a representation of the expression tree after rewriting by the optimizer. .TP \fB\-l\fR Causes line numbers to be maintained for source documents. These are accessible using the extension function saxon:line\-number(). Line numbers are useful when the purpose of the query is to find errors or anomalies in the source XML file. Without this option, line numbers are available while source documents are being parsed and validated, but they are not retained in the tree representation of the document. .TP \fB\-mr\fR classname Use the specified ModuleURIResolver to process all query module URIs. The ModuleURIResolver is a user\-defined class that implements the net.sf.saxon.query.ModuleURIResolver interface. It is invoked to process URIs used in the import module declaration in the query prolog, and (if \fB\-u\fR is also specified, or if the file name begins with http: or file:) to process the URI of the query source file provided on the command line. .TP \fB\-noext\fR Prevents the query calling external Java functions. This is useful for safety if the query is untrusted. .TP \fB\-o\fR filename Send output to named file. In the absence of this option, the results go to standard output. The output format depends on whether the \fB\-wrap\fR option is present. .TP \fB\-p\fR Use the PTreeURIResolver. This option is available in Saxon\-SA only. It cannot be used in conjunction with the \fB\-r\fR option, and it automatically switches on the \fB\-u\fR and \fB\-sa\fR options. The effect is twofold. Firstly, Saxon\-specific file extensions are recognized in URIs (including the URI of the source document on the command line). Currently the only Saxon\-specific file extension is .ptree, which indicates that the source document is supplied in the form of a Saxon PTree. This is a binary representation of an XML document, designed for speed of loading. Secondly, Saxon\-specific query parameters are recognized in a URI. Currently the only query parameter that is recognized is val. This may take the values strict, lax, or strip. For example, source.xml?validation=strict loads a document with strict schema validation. .TP \fB\-pull\fR Execute query in pull mode. This may give performance advantages for certain kinds of query, especially queries that construct intermediate trees in memory. .TP \fB\-r\fR classname Use the specified URIResolver to process all URIs. The URIResolver is a user\-defined class, that implements the URIResolver interface defined in JAXP, whose function is to take a URI supplied as a string, and return a SAX InputSource. It is invoked to process URIs used in the doc() function, and (if \fB\-u\fR is also specified) to process the URI of the source file provided on the command line. .TP \fB\-s\fR filename\-or\-URI Take input from the specified file. If the \fB\-u\fR option is specified, or if the name begins with file: or http:, then the name is assumed to be a URI rather than a filename. This file must contain an XML document. The document node of the document is made available to the query as the context item. The source document can be specified as \- to take the source from standard input. .TP \fB\-sall\fR Strips all whitespace text nodes from source documents before any further processing, regardless of any xml:space attributes in the source document. .TP \fB\-signorable\fR Strips all ignorable whitespace text nodes from source documents before any further processing, regardless of any xml:space attributes in the source document. Whitespace text nodes are ignorable if they appear in elements defined in the DTD or schema as having element\-only content. .TP \fB\-snone\fR Strips no whitespace before further processing. .TP \fB\-strip\fR Equivalent to \fB\-sall\fR: retained for compatibility. .TP \fB\-t\fR Display version and timing information to the standard error output. The output also traces the files that are read and written, and extension modules that are loaded. .TP \fB\-T\fR Enable execution tracing. This will cause a trace of the query execution to be output to the standard error output. The events that are traced are currently function calls (entry and exit) and element construction. .TP \fB\-TJ\fR Switches on tracing of the binding of calls to external Java methods. This is useful when analyzing why Saxon fails to find a Java method to match an extension function call in the stylesheet, or why it chooses one method over another when several are available. .TP \fB\-u\fR Indicates that the name of the source document is a URI; otherwise it is taken as a filename, unless it starts with http: or file:, in which case they it is taken as a URL. .TP \fB\-v\fR Indicates that source documents are to be parsed using a validating parser (this invokes DTD validation, not schema validation). .TP \fB\-val\fR This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. It requests strict validation of source documents using an XML Schema. .TP \fB\-vlax\fR This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. It requests lax validation of source documents using an XML Schema. That is, the document will be validated if a suitable schema is available, and will not be validated otherwise. .TP \fB\-vw\fR Indicates that validation errors found when validating the result tree should be treated as warnings only. This option is available only with the Saxon\-SA version of the command, com.saxonica.Query. .TP \fB\-wrap\fR Wraps the result sequence in an XML element structure that indicates the type of each node or atomic value in the query result. This format can handle any type of query result. In the absence of this option, the command effectively wraps a document{} constructor around the supplied query, so that the result is a single XML document, which is then serialized. This will fail if the query result includes constructs that cannot be added to a document node in this way, notably free\-standing attribute nodes. .TP \fB\-1\fR.1 Allow XML 1.1 and XML Namespaces 1.1 constructs. This option must be set if source documents using XML 1.1 are to be read, or if result documents are to be serialized as XML 1.1. This option also enables use of XML 1.1 constructs within the query itself. .TP \-? Display command syntax .TP query Identifies the file containing the query. Mandatory. The argument can be specified as \- to read the query from standard input. The query can also be specified inline by enclosing it in curly braces (if it contains spaces, you will also need quotes outside the curly braces to keep the command line processor happy). For example java net.sf.saxon.Query {doc('a.xml')//p[1]} selects elements within the file a.xml in the current directory. A param takes the form name=value, name being the name of the parameter, and value the value of the parameter. These parameters are accessible within the query as external variables, using the syntax, provided they are declared in the query prolog. If there is no such declaration, the supplied parameter value is silently ignored. .PP A param preceded by a leading plus sign (+) is interpreted as a filename or directory. The content of the file is parsed as XML, and the resulting document node is passed to the stylesheet as the value of the parameter. If the parameter value is a directory, then all the immediately contained files are parsed as XML, and the resulting sequence of document nodes is passed as the value of the parameter. For example, +lookup=lookup.xml sets the value of the external variable lookup to the document node at the root of the tree representing the parsed contents of the file lookup.xml. .PP A param preceded by a leading exclamation mark is interpreted as a serialization parameter. For example, !indent=yes requests indented output, and !encoding=iso\-8859\-1 requests that the serialized output be in ISO 8859/1 encoding. This is equivalent to specifying the option declaration declare option saxon:output indent=yes; or declare option saxon:output encoding=iso\-8859\-1; in the query prolog. .PP Under Windows, and some other operating systems, it is possible to supply a value containing spaces by enclosing it in double quotes, for example name=John Smith. This is a feature of the operating system shell, not something Saxon does, so it may not work the same way under every operating system. .PP If the parameter name is in a non\-null namespace, the parameter can be given a value using the syntax {uri}localname=value. Here uri is the namespace URI of the parameter's name, and localname is the local part of the name. .PP This applies also to output parameters. For example, you can set the indentation level to 4 by using the parameter !{http://saxon.sf.net/}indent\-spaces=4. For the extended set of output parameters supported by Saxon, see Additional serialization parameters. .SH AUTHOR Michael H. Kay <[email protected]> -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
