3. System properties
Prev | A. Command line options |

### 3. System properties

In principle, there is no need to use the following, very low-level, system properties.

Property name | Value | Description
--- | --- | ---
XSL_FO_PROCESSORS | List of XSL-FO processor names separated by semi-colons ('`;`'). | This property contains the names of all XSL-FO processor plug-ins. Examples: "`FOP;XFC`", "`XEP`". For use by some XSLT style sheets.

XXE_ADDON_DOWNLOAD_LOCATION

List of "`.xxe_addon`" URLs separated by semi-colons ('`;`').

Clicking on the Reset button of the "Install add-on" preferences of the Preferences dialog box resets the list of download URLs to the value specified by this property.

If this property is not set, by default, the list of download URLs is

- http://www.xmlmind.com/xmleditor/_usercontrib/list.xxe_addon

- `http://www.xmlmind.net/xmleditor/_download/list-`${XXE_VERSION}`.xxe_addon` (for example, variable `${XXE_VERSION}` is replaced by "`3_5_2`" if the version of the running XML Editor is v3.5.2)

- http://www.xmlmind.net/xmleditor/_download/list.xxe_addon

XXE_CATALOG_RESOLVER_VERBOSITY | Strictly positive integer (the larger, the more verbose) | Prints on the console messages tracing the resolution by the XML catalog resolver of system identifiers.

XXE_CONFIRM_CREDENTIALS_DELAY

Strictly positive number of milliseconds

Workaround for the following problem: “when opening a document stored on a server requiring user authentication (e.g. a WebDAV server), a user who typed an incorrect username or password is never prompted again for her/his credentials”.

Example: `-DXXE_CONFIRM_CREDENTIALS_DELAY=1000`, means wait for at least 1000 milliseconds before considering that the credentials specified by the user have been accepted by the server.

When system property `XXE_CONFIRM_CREDENTIALS_DELAY` has been specified to an appropriate number of milliseconds, a user who typed an incorrect username or password is automatically prompted again for her/his credentials. However, this workaround, based on a heuristic, may be tricky to configure and may be not usable for some protocols. For example, it seems to work for `HTTP` and it gets in the way for `FTP`.

XXE_DAV_LOCK_OWNER | A free form string, typically an email address. | Used by the WebDAV client. Specifies which string is used by default to identify you as the owner of a lock.
XXE_DAV_TRACE | Any (example: `1`; suffice to set this property). | Causes the WebDAV client to print DAV requests and responses on the console.
XXE_DAV_USE_SIMPLE_REFS | Any (example: `1`; suffice to set this property). | Causes the WebDAV client to use absolute paths rather than full URIs in the `Destination` and `If` headers. Doing this is allowed by RFC 4918, but not by (obsolete) RFC 2518. This may be useful when operating through a reverse proxy that does rewrite the `Host` request header, but not WebDAV-specific headers.

XXE_DAV_URI_ENCODING_USES_8859_1

Any (example: `1`; suffice to set this property).

Used by the WebDAV client.

Specifies that the WebDAV server expects and returns URIs where accented characters (to make it simple) are escaped using the customary %`HH` form but where `HH` is the hexadecimal code of an ISO-8859-1 character.

The standard mandates `HH` to be UTF-8 codes, not ISO-8859-1 codes.

For example, this flag is needed for Apache/mod_dav running on an ``old'' Linux server where the file system encodes filenames using ISO-8859-1.

XXE_FOP_CONFIG

URL of a user-defined FOP configuration file

Specifies the location of a FOP configuration file.

Note that, because this URL is resolved using the XML catalogs of XXE, this allows to bundle a custom FOP configuration file with the FOP plug-in, prior to deploying XXE using Java™ Web Start.

Procedure:

1. Create the custom FOP configuration file in ``FOP_plugin_dir`/conf/fop.conf`.

2. Create XML catalog `fop_catalog.xml` in ``FOP_plugin_dir`/`. This file should contain:

       <catalog
         xmlns="urn:oasis:names:tc:entity:¬
       xmlns:xml:catalog">
         <rewriteURI uriStartString="fop-plugin:"
                     rewritePrefix="."/>
       </catalog>

3. Run deploywebstart in <ttl>XMLmind XML Editor - Configuration and Deployment</ttl>.

4. Add

       <property name="XXE_FOP_CONFIG"
         value="fop-plugin:conf/fop.conf"/>

   to the `xxe.jnlp` file generated by deploywebstart.

XXE_JAVA_IMAGE_TOOLKIT_EXCLUDE | List of file extensions separated by semi-colons ('`;`'). | Example: `-DXXE_JAVA_IMAGE_TOOLKIT_EXCLUDE="bmp;wbmp"` This would prevent the built-in Java™ 1.5 image toolkit from handing BMP images. This is useful in case you find an external image toolkit which handles specified image extensions better than the built-in Java™ image toolkit.
XXE_NETWORK_TIMEOUT | A number of milliseconds. | Specifies the default timeout used for creating network connections and reading responses. A negative or null number means: wait indefinitely. Used at various places in XMLmind XML Editor, for example by WebDAV and FTP virtual drives. Built-in default value is 120,000ms (2mn).

XXE_PREDECLARE_NAMESPACE_PREFIXES

Any value. Suffice for this system property to be set.

Slightly changes the way namespace prefixes are declared in an XML save file, when the document being saved conforms to a DTD.

- `-DXXE_PREDECLARE_NAMESPACE_PREFIXES=1` means: pre-declare on the root element all the namespace prefixes found in the document (regardless on whether this is allowed by the DTD).

- The standard method is: declare a namespace prefix when needed to (regardless on whether this is allowed by the DTD).

Both methods are flawed. In the general case, XXE simply cannot generate XML documents in which the `xmlns` attributes are validated against a DTD.

XXE_XEP_CONFIG | URL of a user-defined XEP configuration file | Same as XXE_FOP_CONFIG, but applies to RenderX XEP rather than to Apache FOP.
javaws.XXE.`*` | - | Reserved. Do not use.

Prev | Up |
2. Environment variables | Home |