Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
////////////////////////////////////////////////////////////////////////
// Copyright (c) 2018-2020 Saxonica Limited
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0.
// If a copy of the MPL was not distributed with this file, You can
// obtain one at http://mozilla.org/MPL/2.0/.
// This Source Code Form is "Incompatible With Secondary Licenses",
// as defined by the Mozilla Public License, v. 2.0.
////////////////////////////////////////////////////////////////////////
package net.sf.saxon.lib;
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
// If you edit this file, your edits WILL BE TERMINATED with
// extreme prejudice by the next build.
/**
* Feature defines a set of constants, representing the details of Saxon configuration
* options which can be supplied to the Saxon method Configuration.setProperty(),
* and to other interfaces
*/
public class Feature {
public final int code;
public final String name;
private Feature(int code, String name) {
this.code = code;
this.name = name;
}
/**
*
ALLOW_EXTERNAL_FUNCTIONS has rather wider effect than the name might suggest.
* It controls whether stylesheets are able to access external resources in the server environment.
*
More specifically, if set to false it disallows all of the
* following:
*
*
With SaxonJ, calls to reflexive Java extension functions
*
Use of the XSLT system-property() function to access Java system
* properties
*
Use of the Saxon SQL extension library
*
Use of the EXPath File library
*
Use of a URI in the href attribute of an xsl:result-document instruction
*
Calls to XSLT extension instructions
*
*
The default value is true. The setting false is recommended in an
* environment where untrusted stylesheets may be executed.
*
This option does not disable use of the doc() function or similar
* functions to access the filestore of the machine where the transformation or query
* is running. That should be done using a user-supplied URIResolver.
*
Note that integrated extension functions are trusted; calls to such functions are
* allowed even if this configuration option is false. In cases where an integrated
* extension function is used to load and execute untrusted code, it should check this
* configuration option before doing so.
*
If the value of the property is false, then it will also be set to false on any new
* Configuration created using the fn:transform() function.
*
**/
public final static Feature ALLOW_EXTERNAL_FUNCTIONS = new Feature(1, "http://saxon.sf.net/feature/allow-external-functions");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
ALLOW_MULTITHREADING determines whether multi-threading is allowed.
*
If true (the default), the presence of the attribute saxon:threads="N"
* on an xsl:for-each instruction, when running under Saxon-EE, causes
* multi-threaded execution. If set to false, the value of the
* saxon:threads argument is ignored.
*
Setting the value to false also disables asynchronous processing of
* xsl:result-document instructions.
*
The default value is true if Saxon-EE is in use, false otherwise.
*
**/
public final static Feature ALLOW_MULTITHREADING = new Feature(2, "http://saxon.sf.net/feature/allow-multithreading");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
ALLOW_OLD_JAVA_URI_FORMAT determines whether extension function calls to
* dynamically-loaded Java extension functions may use the URI format supported in
* older Saxon releases.
*
If the value is false (the default), the only URI format accepted is (for example)
* "java:java.util.Date" - that is, a URI consisting of the string "java:" followed by
* the Java qualified class name of the class containing the implementation of the
* extension function.
*
If the value is true, then in addition to this format, the following are accepted:
* (a) the Java class name on its own ("java.util.Date"), and (b) any URI in which the
* Java class name follows the last "/" character (for example
* "http://my.com/extensions/java.util.Date"). This last format was originally provided
* for compatibility with xt and xalan, but it causes problems because it leads to
* unnecessary attempts to load spurious classes when the user did not intend the URI
* to represent a dynamically-loaded Java class.
*
**/
public final static Feature ALLOW_OLD_JAVA_URI_FORMAT = new Feature(3, "http://saxon.sf.net/feature/allow-old-java-uri-format");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This flag must be set to enable use of extensions to XPath, XQuery and XSLT
* syntax that go beyond what is allowed by the extensibility mechanisms in the spec.
* In some cases these extensions are experimental and may not be carried forward to future
* Saxon releases.
*
Syntax extensions in Saxon 10 include the use of type aliases (type(...) where
* an item type is expected, and declare type NAME = item-type in the XQuery Prolog);
* and simple inline functions (for example .{. + 1}).
*
**/
public final static Feature ALLOW_SYNTAX_EXTENSIONS = new Feature(4, "http://saxon.sf.net/feature/allowSyntaxExtensions");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
ASSERTIONS_CAN_SEE_COMMENTS determines whether comment and processing instructions in
* a document being validated are visible to assertions in an XSD 1.1 schema.
*
If the value is false (the default), comments and processing instructions are
* stripped from the view of the document that is made visible to the XPath expression
* that implements the assertion. If this creates adjacent text nodes, they are
* collapsed into a single text node.
*
If the value is true, then comments and processing instructions are visible to the
* XPath assertion.
*
**/
public final static Feature ASSERTIONS_CAN_SEE_COMMENTS = new Feature(5, "http://saxon.sf.net/feature/assertionsCanSeeComments");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
The supplied CollationURIResolver is used to process any collation URIs
* found in the query or stylesheet, returning an object of class
* {@link net.sf.saxon.lib.StringCollator} that implements the requested
* collation.
*
**/
public final static Feature COLLATION_URI_RESOLVER = new Feature(6, "http://saxon.sf.net/feature/collation-uri-resolver");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
The supplied class is instantiated and the resulting instance is used as the value of
* the {@link net.sf.saxon.lib.Feature#COLLATION_URI_RESOLVER} property.
*
**/
public final static Feature COLLATION_URI_RESOLVER_CLASS = new Feature(7, "http://saxon.sf.net/feature/collation-uri-resolver-class");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
The supplied CollectionFinder is used to retrieve a {@link net.sf.saxon.lib.ResourceCollection} object given by any URI defined in
* calls to the collection() or the uri-collection() function.
*
If the argument is not specified then a default ResourceCollection should be handled.
* CollectionFinder returns a {@link net.sf.saxon.lib.ResourceCollection} which is used to map the URI of collection into a
* sequence of {@link net.sf.saxon.lib.Resource} objects
* (which are then resolved in the same way as URIs passed to the doc()
* function), or it may return an item (typically a node but can handle JSON documents).
*
**/
public final static Feature COLLECTION_FINDER = new Feature(8, "http://saxon.sf.net/feature/collection-finder");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
The supplied class is instantiated and the resulting instance is used as the value of
* the {@link net.sf.saxon.lib.Feature#COLLECTION_FINDER} property.
*
**/
public final static Feature COLLECTION_FINDER_CLASS = new Feature(9, "http://saxon.sf.net/feature/collection-finder-class");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
If run-time tracing of stylesheet or query execution is required, then the code must
* be compiled with tracing enabled.
*
Default is false. This option causes code to be
* compiled that makes calls to a {@link net.sf.saxon.lib.TraceListener}, but this
* has no effect unless a TraceListener is registered at execution
* time.
*
**/
public final static Feature COMPILE_WITH_TRACING = new Feature(12, "http://saxon.sf.net/feature/compile-with-tracing");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This attribute cannot be set on the {@link net.sf.saxon.Configuration} itself,
* but it can be set on various JAXP factory objects such as a
* TransformerFactory or DocumentBuilderFactory, to
* ensure that several such factories use the same Configuration.
*
Note that other configuration options are held in the Configuration object,
* so setting this attribute will cancel all others that have been set. Also, if two
* factories share the same Configuration, then setting an attribute on
* one affects all the others.
*
**/
public final static Feature CONFIGURATION = new Feature(13, "http://saxon.sf.net/feature/configuration");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Defines a configuration file to be applied to the configuration.
*
This attribute cannot be set on the {@link net.sf.saxon.Configuration} itself, but it can be
* set on various JAXP factory objects such as a TransformerFactory or
* DocumentBuilderFactory. It is particularly useful when running
* transformations via the Ant xslt task, where it can be set as follows to define all
* configuration settings:
*
**/
public final static Feature CONFIGURATION_FILE = new Feature(14, "http://saxon.sf.net/feature/configuration-file");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option is set to indicate that bytecode generation should be run in debugging
* mode; it injects diagnostic tracing calls into the generated bytecode. This should
* be used only if requested by Saxonica support to diagnose a problem related to
* bytecode generation.
*
**/
public final static Feature DEBUG_BYTE_CODE = new Feature(15, "http://saxon.sf.net/feature/debugByteCode");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option is relevant only if DISPLAY_BYTE_CODE is set to true. It
* defines a directory to which files containing bytecode in human-readable form will
* be written. There will be one such file for each generated class, with a filename
* designed to give some kind of clue as to its relationship to the source code.
*
The default value is the directory saxonByteCode within the current
* working directory.
*
The named directory is created if it does not already exist.
*
Because the generation of class names involves random numbers, files will tend to
* accumulate in the supplied directory, even when the same source code is compiled
* repeatedly.
*
**/
public final static Feature DEBUG_BYTE_CODE_DIR = new Feature(16, "http://saxon.sf.net/feature/debugByteCodeDir");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option determines the collation that is used for comparing strings when no
* explicit collation is requested. It is not necessary for this collation to exist (or
* to have been registered) when setting this option; it only needs to exist by the
* time it is used.
*
In XSLT it is possible to override this setting using the
* [xsl:]default-collation attribute on any stylesheet element. In
* XQuery, it can be overridden using the declare default collation
* declaration in the query prolog, or via a setter method in class
* {@link net.sf.saxon.query.StaticQueryContext}.
*
If no value is specified, the Unicode codepoint collation is used.
*
**/
public final static Feature DEFAULT_COLLATION = new Feature(17, "http://saxon.sf.net/feature/defaultCollation");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This determines the collection that is used when the fn:collection()
* function is called with no arguments; the effect is the same as if it were called
* passing the URI that is the value of this configuration property.
*
**/
public final static Feature DEFAULT_COLLECTION = new Feature(18, "http://saxon.sf.net/feature/defaultCollection");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This determines the country that is used by format-date() and similar
* functions if no country code is supplied explicitly. If no value is given for this
* property, the default is taken from the Java Locale, which in turn typically depends
* on settings for the current user in the operating system.
*
**/
public final static Feature DEFAULT_COUNTRY = new Feature(19, "http://saxon.sf.net/feature/defaultCountry");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option determines the language that is used by format-date(),
* xsl:number and similar constructs if no language code is supplied
* explicitly. If no value is given for this property, the default is taken from the
* Java Locale, which in turn typically depends on settings for the current user in the
* operating system.
*
**/
public final static Feature DEFAULT_LANGUAGE = new Feature(20, "http://saxon.sf.net/feature/defaultLanguage");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Determines which regular expression engine should be used for evaluating regular expressions occuring in constructs
* such as fn:matches(), fn:replace, and xsl:analyze-string, and also
* in the pattern facet of a schema.
*
On the Java platform the permitted values are "S" (default), and "J". The value "J" selects the regex engine
* provided in the JDK in preference to the Saxon regular expression engine. This means that regular expressions must
* follow the Java syntax and semantics rather than the XPath syntax and semantics.
*
On the .NET platform the permitted values are "S" (default), "J", and "N". The value "J" selects the regex engine
* provided in the IKVMC run-time, which is derived from OpenJDK. The value "N" selects the regex engine provided
* in the Microsoft .NET platform. In each case, the regular expression must follow the syntax and semantics of the selected
* regex engine.
*
The choice of regular expression may be overridden in a particular invocation by appending the value ";s",
* ";j", or ";n" to the flags argument of the relevant call. (This does not apply to XSD patterns, where no flags argument is available)
*
Use of this feature is not conformant with W3C specifications. Use of the setting "N", however, can be useful
* when schemas have been written with the Microsoft schema processor in mind, since this uses the Microsoft regular
* expression dialect rather than the W3C dialect.
*
**/
public final static Feature DEFAULT_REGEX_ENGINE = new Feature(21, "http://saxon.sf.net/feature/defaultRegexEngine");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option disables the xsl:evaluate instruction.
*
If set at stylesheet compile time, the feature is statically disabled. If set at
* run-time it is dynamically disabled. (These terms are defined in the XSLT 3.0 spec.)
* The feature is always disabled (statically) in Saxon-HE.
*
**/
public final static Feature DISABLE_XSL_EVALUATE = new Feature(22, "http://saxon.sf.net/feature/disableXslEvaluate");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option is set to indicate that bytecode generation should be run in display
* mode. The effect is to output files (one per class) containing a human-readable
* print of the generated bytecode. The files are placed in the directory identified by
* the DEBUG_BYTE_CODE_DIR option.
*
**/
public final static Feature DISPLAY_BYTE_CODE = new Feature(23, "http://saxon.sf.net/feature/displayByteCode");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
If true, the XML parser is requested to perform validation of source documents
* against their DTD. Default is false.
*
This option establishes a default for use whenever source documents (not stylesheets
* or schema documents) are parsed. The option can be overridden for individual
* documents by setting the {@link net.sf.saxon.lib.ParseOptions} for that
* individual document, for example from a URIResolver.
*
**/
public final static Feature DTD_VALIDATION = new Feature(24, "http://saxon.sf.net/feature/validation");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
This option determines whether DTD validation failures should be treated as
* recoverable. If the option is set, a validation failure is reported as a warning
* rather than an error. The default is false.
*
This option establishes a default for use whenever source documents (not stylesheets
* or schema documents) are parsed. The option can be overridden for individual
* documents by setting the {@link net.sf.saxon.lib.ParseOptions} for that
* individual document, for example from a URIResolver.
*
**/
public final static Feature DTD_VALIDATION_RECOVERABLE = new Feature(25, "http://saxon.sf.net/feature/dtd-validation-recoverable");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Forces Saxon to do eager evaluation of expressions in contexts where normally it would do lazy evaluation,
* for example when evaluating variables and function results. This can make for easier debugging.
*
Note that this only applies to situations where Saxon would normally save a Closure
* object as the result of an expression. It does not prevent Saxon from using pipelined evaluation of
* intermediate expressions using iterators.
*
**/
public final static Feature EAGER_EVALUATION = new Feature(26, "http://saxon.sf.net/feature/eagerEvaluation");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
The supplied class is instantiated and the resulting EntityResolver is
* used whenever Saxon itself creates an XMLReader for parsing source
* documents. It is not used with a user-supplied XMLReader.
*
The default value is {@link net.sf.saxon.lib.StandardEntityResolver}. This is an entity
* resolver that recognizes the names of many standard W3C DTDs and external entity
* files, and resolves them against local copies issued with the Saxon software, to
* avoid the need to fetch them from the web.
*
The property can be set to a zero-length string, in which case no
* EntityResolver will be used.
*
*
**/
public final static Feature ENTITY_RESOLVER_CLASS = new Feature(27, "http://saxon.sf.net/feature/entityResolverClass");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Setting the ENVIRONMENT_VARIABLE_RESOLVER causes the supplied object to
* be registered as the environment variable resolver for the
* Configuration. The setting is global: it affects all queries and
* transformations using this configuration.
*
The environment variable resolver is used when the XPath functions
* available-environment-variables() or
* environment-variable() are called. Saxon essentially delegates the
* evaluation of the function to the external resolver.
*
**/
public final static Feature ENVIRONMENT_VARIABLE_RESOLVER = new Feature(28, "http://saxon.sf.net/feature/environmentVariableResolver");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Setting ENVIRONMENT_VARIABLE_RESOLVER_CLASS causes an instance of the
* supplied class to be created, and registered as the environment variable resolver
* for the Configuration. The setting is global: it affects all queries
* and transformations using this configuration.
*
The environment variable resolver is used when the XPath functions
* available-environment-variables() or
* environment-variable() are called. Saxon essentially delegates the
* evaluation of the function to the external resolver.
*
**/
public final static Feature ENVIRONMENT_VARIABLE_RESOLVER_CLASS = new Feature(29, "http://saxon.sf.net/feature/environmentVariableResolverClass");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
ERROR_LISTENER_CLASS is the name of the class used to implement the JAXP
* ErrorListener. This is used both at compile time and at run-time.
*
Currently if this option is specified, the class is instantiated, and the same
* instance is used for all processes running under this configuration. This may change
* in future so that a new instance is created for each compilation or evaluation.
*
Finer control can be obtained by setting the ErrorListener for a
* specific XSLT or XQuery compilation or evaluation.
*
**/
public final static Feature ERROR_LISTENER_CLASS = new Feature(30, "http://saxon.sf.net/feature/errorListenerClass");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
EXPAND_ATTRIBUTE_DEFAULTS determines whether fixed and default values
* defined in a schema or DTD will be expanded (both on input and on output documents,
* if validation is requested).
*
By default (and for conformance with the specification)
* validation against a DTD or schema will cause default values defined in the schema
* or DTD to be inserted into the document. Setting this feature to false suppresses
* this behavior. In the case of DTD-defined defaults this only works if the XML parser
* reports whether each attribute was specified in the source or generated by expanding
* a default value. Not all XML parsers report this information.
*
**/
public final static Feature EXPAND_ATTRIBUTE_DEFAULTS = new Feature(31, "http://saxon.sf.net/feature/expandAttributeDefaults");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
EXPATH_FILE_DELETE_TEMPORARY_FILES determines whether temporary files
* and directories created in the EXPath File module should be automatically deleted on
* closure of the JVM.
*
The default value is false, to align with the standard. The setting
* false is recommended when external 'sweep-up' features aren't
* available.
*
**/
public final static Feature EXPATH_FILE_DELETE_TEMPORARY_FILES = new Feature(32, "http://saxon.sf.net/feature/expathFileDeleteTemporaryFiles");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
By default, Saxon-EE attempts to generate Java bytecode for evaluation of parts of a
* query or stylesheet that are amenable to such treatment. Setting this option to
* false disables this.
*
For backwards compatibility, this option when used at the level of Configuration.setConfigurationProperty()
* can also be used to set the value of THRESHOLD_FOR_HOTSPOT_BYTECODE. If the value on that interface is supplied
* as an integer (or a string in the form of an integer) then a value of 1 or more sets the threshold for hotspot detection, while
* a value of zero or less disables bytecode generation entirely. On other interfaces the value of the property must be a boolean.
*
**/
public final static Feature GENERATE_BYTE_CODE = new Feature(33, "http://saxon.sf.net/feature/generateByteCode");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
If this option is set to true, then when a SAXSource is supplied as the
* input to an XSLT transformation, Saxon will ignore the XMLReader
* supplied in the SAXSource (in fact, it will modify the supplied
* SAXSource setting the XMLReader to null) and use an
* XMLReader created using the value of the
* SOURCE_PARSER_CLASS option in preference.
*
The defining use case for this feature is when calling a Saxon transformation from
* Ant. Ant always supplies the source document as a SAXSource using a
* parser instantiated using the default JAXP mechanism. A different parser set using
* the property http://saxon.sf.net/feature/sourceParserClass will
* normally be ignored in this case; setting the ignoreSAXSourceParser
* option overrides this. This is especially useful if the input format is not in fact
* XML, but some other format converted to a SAX event stream by means of a custom
* parser.
*
**/
public final static Feature IGNORE_SAX_SOURCE_PARSER = new Feature(34, "http://saxon.sf.net/feature/ignoreSAXSourceParser");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
IMPLICIT_SCHEMA_IMPORTS allows reference to schema components without an xs:import for the relevant namespace being
* present in the containing schema document.
*
This only works if the referenced components are already present among the schema components known to the configuration, perhaps
* because they were part of a different schema, or because there are cyclic references within a schema.
*
This option is not conformant with the XSD specification, which requires explicit xs:import declarations
* for all cross-namespace component references. However, some "industry-standard" schemas are known to violate this rule,
* and setting this option allows such schemas to be loaded by Saxon.
*
**/
public final static Feature IMPLICIT_SCHEMA_IMPORTS = new Feature(35, "http://saxon.sf.net/feature/implicitSchemaImports");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
LAZY_CONSTRUCTION_MODE determines whether temporary trees are
* constructed lazily. The default setting is false; there are a few situations (but
* not many) where setting this to true can give a performance benefit (especially a
* memory saving).
*
The option is most likely to be effective when executing XQuery in "pull" mode, that
* is, when the client calls the query processor to deliver the result as a stream of
* nodes, rather than running the query and piping the results into a serializer.
*
**/
public final static Feature LAZY_CONSTRUCTION_MODE = new Feature(36, "http://saxon.sf.net/feature/lazyConstructionMode");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
LICENSE_FILE_LOCATION holds the filename in which the Saxon license file
* is held.
*
This is the full file name, for example c:/saxon/license/license.lic.
* Setting this property causes Saxon to
* immediately read the specified file and register the license data, assuming it can
* be found at this location. The property is not recognized for reading, and it is not
* recognized for writing except in Saxon-PE and Saxon-EE.
*
**/
public final static Feature LICENSE_FILE_LOCATION = new Feature(37, "http://saxon.sf.net/feature/licenseFileLocation");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Default is false. If true, line and column number information is retained for all
* source documents. This information is accessible using the
* saxon:line-number() and saxon:column-number()
* extension functions.
*
Note that the information is only as good as the XML parser supplies. SAX parsers
* generally report the position of an element node using the line and column number of
* the ">" character that forms the last character of the start tag.
*
When this option is set, location information attached to a node (system ID, line
* number, and column number) is retained when the node is copied. This has the side effect
* that the base URI of a node is also copied, which in some cases runs contrary to the
* XSLT or XQuery specification.
*
**/
public final static Feature LINE_NUMBERING = new Feature(38, "http://saxon.sf.net/feature/linenumbering");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Setting the MARK_DEFAULTED_ATTRIBUTES option causes Saxon to retain details of attributes
* that were notified by the XML parser as being defaulted (that is, the attribute was not present in the instance
* document but was defined by a default value in a DTD or schema). This information is available to applications
* via the saxon:is-defaulted() extension function.
*
Note: information about defaulted attributes is retained automatically where the attribute is processed
* using Saxon's schema processor; but in the case where the information comes from an external XML parser, it
* is retained only if this option is set.
*
**/
public final static Feature MARK_DEFAULTED_ATTRIBUTES = new Feature(39, "http://saxon.sf.net/feature/markDefaultedAttributes");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Places a limit on the number of classes for which Saxon will generate bytecode.
*
If bytecode generation is enabled, Saxon will generate bytecode for frequently used constructs appearing
* in stylesheets or queries. This can become problematic if a configuration uses a very large number
* of different stylesheets and queries, because it creates memory pressure (in some environments classes
* are never garbage collected). When this limit (which defaults to 10,000) is exceeded, no more bytecode
* is generated, and queries/stylesheets are interpreted instead.
*
**/
public final static Feature MAX_COMPILED_CLASSES = new Feature(40, "http://saxon.sf.net/feature/maxCompiledClasses");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
From Saxon 11.1, this option has no effect.
*
*
**/
public final static Feature MESSAGE_EMITTER_CLASS = new Feature(41, "http://saxon.sf.net/feature/messageEmitterClass");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Affects XQuery only. An instance of a user-written class implementing Saxon's
* {@link net.sf.saxon.lib.ModuleURIResolver} interface. This is used to
* process any URIs used in import module directives in XQuery.
*
**/
public final static Feature MODULE_URI_RESOLVER = new Feature(42, "http://saxon.sf.net/feature/moduleURIResolver");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Affects XQuery only. The name of a user-written class implementing Saxon's
* {@link net.sf.saxon.lib.ModuleURIResolver} interface. This is used to
* process any URIs used in import module directives in XQuery.
*
**/
public final static Feature MODULE_URI_RESOLVER_CLASS = new Feature(43, "http://saxon.sf.net/feature/moduleURIResolverClass");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
When set from the Transform or Query command line, a report on bytecode generation is
* produced at the end of the transformation or query.
*
When set from an application, the bytecode report is produced only on request, by
* calling Configuration.createByteCodeReport(fileName).
*
The bytecode report is an XML file containing one entry for each expression that has
* been compiled into bytecode. Each entry contains the following details, where
* applicable:
*
*
text Abbreviated text of the expression
*
intCount Number of times the expression was evaluated in the interpreter
*
intTime Cumulative time spent evaluating the expression (including subexpressions) in the interpreter
*
bcCount Number of times the expression was evaluated as byte-code
*
bcTime Cumulative time spent evaluating the expression (including subexpressions) as byte-code
*
compileTime Time spent generating bytecode for the expression
*
ratio Average byte-code execution time as a proportion of average interpreted execution time
*
ebv Number of evaluations of the expressions effectiveBooleanValue() method
*
eval Number of evaluations of the expressions evaluateItem() method
*
iterate Number of evaluations of the expressions iterate() method
*
process Number of evaluations of the expressions process() method
*
module URI of the module containing the expression
*
line Line number of the expression within this module
*
*
**/
public final static Feature MONITOR_HOT_SPOT_BYTE_CODE = new Feature(44, "http://saxon.sf.net/feature/monitorHotSpotByteCode");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Affects schema construction (whether for standalone validation, or in the context of
* XSLT or XQuery).
*
If set to true, the schema processor attempts to fetch a schema
* document appearing in an xs:import directive, whether or not a schema
* for that namespace has already been loaded, unless the absolute URI formed from the
* schemaLocation is the same as the absolute URI that was used to
* load that namespace. If set to false, the schema processor ignores the
* schemaLocation on an xs:import declaration if schema
* components for the requested namespace are already available. Note that setting the
* value to true might cause spurious errors due to like-named schema components being
* loaded more than once. On the other hand, setting the value to false might result in
* validation failing because schema components are missing.
*
Note: Both settings are conformant with the W3C recommendation, which leaves the
* details implementation-defined. It is possible (and advisable) to write schemas in
* such a way that this setting makes no difference, by ensuring that all imports for a
* particular namespace go via a "home" schema document for that namespace, where the
* home schema document contains xs:include declarations for all the
* schema documents defining components in that namespace.
*
**/
public final static Feature MULTIPLE_SCHEMA_IMPORTS = new Feature(45, "http://saxon.sf.net/feature/multipleSchemaImports");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
Indicates that the supplied NamePool should be used as the target
* (run-time) NamePool by all stylesheets compiled (using
* newTemplates()) after this call on setAttribute.
*
Normally a single system-allocated NamePool is used for all stylesheets
* compiled while the Java VM remains loaded; this attribute allows user control over
* the allocation of name pools. Note that source trees used as input to a
* transformation must be built using the same NamePool that is used when
* the stylesheet is compiled: this will happen automatically if the input to a
* transformation is supplied as a SAXSource or StreamSource
* but it is under user control if you build the source tree yourself.
*
This option can be used to make two Configuration objects share a
* NamePool even though they differ in other respects.
*
**/
public final static Feature NAME_POOL = new Feature(46, "http://saxon.sf.net/feature/namePool");
// AUTO-GENERATED FROM FeatureKeys.xml - DO NOT EDIT THIS FILE
/**
*
OCCURRENCE_LIMITS determines the largest values of
* minOccurs and maxOccurs that can be accommodated when
* compiling an "expanded" finite state machine to represent an XSD content model
* grammar.
*
These limits do not apply in the common cases where the grammar can be
* implemented using a counting finite-state-machine, but in those cases where this is
* not possible, any minOccurs value greater than the first integer is
* reduced to the value of the first integer, and any maxOccurs value
* greater than the second integer is treated as "unbounded".
*
Setting these values too high may cause an OutOfMemoryException since
* the size of the finite state machine constructed by Saxon increases linearly with
* the values of minOccurs and maxOccurs.
