Hello community, here is the log from the commit of package saxon9 for openSUSE:Factory checked in at 2012-11-12 12:05:12 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/saxon9 (Old) and /work/SRC/openSUSE:Factory/.saxon9.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "saxon9", Maintainer is "" Changes: -------- New Changes file: --- /dev/null 2012-10-22 00:44:18.403455820 +0200 +++ /work/SRC/openSUSE:Factory/.saxon9.new/saxon9.changes 2012-11-12 12:05:14.000000000 +0100 @@ -0,0 +1,140 @@ +------------------------------------------------------------------- +Wed Oct 31 07:31:49 UTC 2012 - [email protected] + +- update to current maintenance release 9.4.0.4 + * no changelog available +- rename to saxon9 to be able to reintroduce saxon6 (XSLT 1.0) + a request from documentation team (bnc#780666) + +------------------------------------------------------------------- +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 + +------------------------------------------------------------------- +Wed Dec 2 18:50:44 UTC 2009 - [email protected] + +- update patches, fix build + +------------------------------------------------------------------- +Mon Mar 10 12:46:08 CET 2008 - [email protected] + +- downgrade to version 6.5.5, moved Saxon 8.x to separate saxon8 + package +- based on the JPackage project, dropped two patches + (tinytree.patch) (fragmentval.patch) +- Saxon 6 is needed because, for example, the DocBook stylesheets + have some JAR files which contain extension functions written + only for Saxon 6. These functions provide useful methods for + DocBook processing. However, these are not compatible + with the latest Saxon package. + +------------------------------------------------------------------- +Wed Feb 6 14:14:44 CET 2008 - [email protected] + +- BuildRequires: java-1.6.0-devel + +------------------------------------------------------------------- +Wed May 23 12:07:12 CEST 2007 - [email protected] + +- make rpmllint happy: + - delete windows '\r' from doc files + - index jars + - faster compiling + +------------------------------------------------------------------- +Thu Mar 29 12:15:40 CEST 2007 - [email protected] + +- added unzip to build reqs + +------------------------------------------------------------------- +Wed Oct 4 20:09:54 CEST 2006 - [email protected] + +- update to saxon 8.8 +- build from source (no binary package) + +------------------------------------------------------------------- +Tue Mar 21 14:21:41 CET 2006 - [email protected] + +- removed setJava call in wrapper script (Bug #158699) + +------------------------------------------------------------------- +Wed Jan 25 21:47:42 CET 2006 - [email protected] + +- converted neededforbuild to BuildRequires + +------------------------------------------------------------------- +Fri Feb 27 20:02:57 CET 2004 - [email protected] + +- updated to the version 6.5.3 [#35119] + * fixes 28 bugs found in Saxon 6.5.2 +- added a missing prebuilt optional saxon-fop.jar +- fixed path to saxon jars in README.SuSE + +------------------------------------------------------------------- +Tue Feb 24 13:27:03 CET 2004 - [email protected] + +- building as non-root + +------------------------------------------------------------------- +Mon Nov 25 15:39:19 CET 2002 - [email protected] + +- added the script saxon to use StyleSheets [#21801] +- improved README.SuSE +- classes moved from /usr/lib to /usr/share + +------------------------------------------------------------------- +Mon Aug 05 17:33:49 CEST 2002 - [email protected] + +- updated to bugfix version 6.5.2 +- small improvent in README.SuSE (run setJava with new better option) + +------------------------------------------------------------------- +Wed Feb 6 18:21:32 CET 2002 - [email protected] + +- updated to version 6.5: + * fixed number of bugs + * important incompatible change for XSLT conformance reasons + * you can find details on the page: + file:/usr/share/doc/packages/saxon/doc/changes.html +- moved to noarch + +------------------------------------------------------------------- +Wed Nov 28 15:39:07 CET 2001 - [email protected] + +- Update to version 6.4.4: + - 20% performance boost. + - Support JDOM. +- Provide convenience link (/usr/lib/saxon -> + /usr/lib/saxon-%{version}). + +------------------------------------------------------------------- +Wed Nov 21 14:08:06 CET 2001 - [email protected] + +- requires changed from java2 to more universal jre1.3.x +- added README.SuSE + +------------------------------------------------------------------- +Wed May 23 15:24:05 CEST 2001 - [email protected] + +- Initial SuSE package: Version 6.3; long pending bug partly resolved + [#291]. + + New: ---- saxon-he-9.4.0.4.pom saxon-resources9-4.zip saxon9-4-0-4source.zip saxon9.1 saxon9.build.script saxon9.changes saxon9.saxon.script saxon9.saxonq.script saxon9.spec saxon9q.1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ saxon9.spec ++++++ # # spec file for package saxon9 # # 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 # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # Summary: The SAXON XSLT Processor from Michael Kay License: MPL-1.0 and Apache-2.0 Group: Productivity/Publishing/XML # net.sf.saxon.om.XMLChar is from ASL-licensed Xerces Name: saxon9 Version: 9.4.0.4 Release: 0 Url: http://saxon.sourceforge.net/ #Source0: https://downloads.sourceforge.net/project/saxon/Saxon-HE/9.3/saxon9-4-0-4source.zip Source0: saxon9-4-0-4source.zip Source1: %{name}.saxon.script 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.4/saxon-resources9-4.zip #Made from original pom file #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 Source7: saxon-he-9.4.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: 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} Provides: saxon = %{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 most recent version of the open-source implementation of XSLT 2.0 and XPath 2.0, and XQuery 1.0. This provides the "basic" conformance level of these languages: in effect, this provides all the features of the languages except schema-aware processing. This version reflects the syntax of the final XSLT 2.0, XQuery 1.0, and XPath 2.0 Recommendations of 23 January 2007 as amended in the second editions of those specifications where appropriate. %package manual Summary: Manual for %{name} Group: Productivity/Publishing/XML %description manual Manual for %{name}. %package javadoc Summary: Javadoc for %{name} Group: Productivity/Publishing/XML %description javadoc Javadoc for %{name}. %package demo Summary: Demos for %{name} Group: Productivity/Publishing/XML Requires: %{name} = %{version}-%{release} %description demo Demonstrations and samples for %{name}. %package scripts Summary: Utility scripts for %{name} Group: Productivity/Publishing/XML Requires: %{name} = %{version}-%{release} Requires: jpackage-utils >= 1.6 %description scripts Utility scripts for %{name}. %prep %setup -q -c 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 docs/api find . \( -name "*.jar" -name "*.pyc" \) -delete %build 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 xml-commons-resolver12) ant \ -Dj2se.javadoc=%{_javadocdir}/java \ -Djdom.javadoc=%{_javadocdir}/jdom %install # jars mkdir -p $RPM_BUILD_ROOT%{_javadir} cp -p build/lib/saxon.jar $RPM_BUILD_ROOT%{_javadir}/%{name}.jar # javadoc 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} 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 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 # 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 %post update-alternatives --install %{_javadir}/jaxp_transform_impl.jar \ jaxp_transform_impl %{_javadir}/%{name}.jar 25 %preun { [ $1 -eq 0 ] || exit 0 update-alternatives --remove jaxp_transform_impl %{_javadir}/%{name}.jar } >/dev/null 2>&1 || : %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 %{_mavenpomdir}/JPP-%{name}.pom %{_mavendepmapfragdir}/%{name} %ghost %{_javadir}/jaxp_transform_impl.jar %files manual %defattr(0644,root,root,0755) %doc doc/*.html %files javadoc %defattr(0644,root,root,0755) %doc %{_javadocdir}/%{name} %files demo %defattr(0644,root,root,0755) %{_datadir}/%{name} %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 ++++++ saxon9.1 ++++++ .\" Kudos to: xsltproc(1), help2man, .\" http://www.saxonica.com/documentation/using-xsl/commandline.html .TH SAXON8 "1" "March 2006" "8.7" "User Commands" .SH NAME saxon8 \- manual page for saxon8 .SH SYNOPSIS .B saxon8 [\fIoptions\fR] \fIsource-document stylesheet \fR[ \fIparams\fR...] .SH DESCRIPTION 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. 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\-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 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\-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. 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. 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 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\-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 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 /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 Michael H. Kay <[email protected]> ++++++ saxon9.build.script ++++++ <!-- simple generic build file --> <project name="saxon" default="all" basedir="."> <!-- Properties --> <property name="name" value="saxon"/> <property name="src" value="src"/> <property name="build" value="build"/> <property name="build.classes" value="${build}/classes"/> <property name="build.doc" value="${build}/api"/> <property name="build.lib" value="${build}/lib"/> <property name="j2se.javadoc" value="/usr/share/javadoc/j2se"/> <property name="jdom.javadoc" value="/usr/share/javadoc/jdom"/> <property name="fop.javadoc" value="/usr/share/javadoc/fop"/> <!-- Targets --> <!-- Prepare build directories --> <target name="prepare"> <mkdir dir="${src}"/> <mkdir dir="${build}"/> <mkdir dir="${build.classes}"/> <mkdir dir="${build.lib}"/> <mkdir dir="${build.doc}"/> <copy todir="${src}"> <fileset dir="." includes="com/**,org/**,net/**"/> </copy> </target> <!-- Kill all the created directories --> <target name="clean"> <delete dir="${build}"/> <delete dir="${src}"/> </target> <!-- Build classes --> <target name="classes" depends="prepare"> <javac srcdir="${src}" destdir="${build.classes}" encoding="ISO-8859-1"/> </target> <!-- Build jar archives --> <target name="jar" depends="classes"> <jar jarfile="${build.lib}/${name}.jar" basedir="${build.classes}"> <manifest> <attribute name="Main-Class" value="net.sf.saxon.Transform" /> </manifest> </jar> </target> <!-- Build the full JavaDocs --> <target name="javadoc" depends="prepare"> <javadoc sourcepath="${src}" destdir="${build.doc}" doctitle="${name} JavaDoc" windowtitle="${name} JavaDoc" package="true" author="true" version="true" packagenames="net.sf.saxon.*,org.w3c.xsl.*" encoding="ISO-8859-1" > <link href="${j2se.javadoc}"/> <link href="${jdom.javadoc}"/> <link href="${fop.javadoc}"/> </javadoc> </target> <!-- Build everything --> <target name="all" depends="jar,javadoc"/> </project> ++++++ saxon9.saxon.script ++++++ #!/bin/sh # # saxon script # JPackage Project <http://www.jpackage.org/> . /usr/share/java-utils/java-functions MAIN_CLASS=net.sf.saxon.Transform 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 "$@" ++++++ saxon9.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 "$@" ++++++ saxon9q.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]
