Sitemap

### Features

• Implemented basic support for "available collections" in the XQuery dynamic context.
• Implemented basic support for "available documents" in the XQuery dynamic context.
• Implemented basic support for "available text resources" in the XQuery dynamic context.
• Implemented support for the collation used in the XQTS (XQuery Test Suite) 3.1.
• Incorporated from 4.3.0:
  • Upgraded to Apache Xerces 2.12.0. eXist-db now includes XML Schema 1.1 support.
  • Improved the Remote XML:DB API "networking error" messages to be more descriptive.
  • Test errors are now summarised in XQSuite XML output.

### Bug fixes

• Fixed a locking issue in the XML:DB Local API when storing XML documents.
• Fixed an NPE which manifested when storing binary documents when preserve-on-copy was enabled.
• Incorporated from 4.3.1:
  • Fixed a regression introduced in eXist-db 4.3.0, where the type conversion of non-empty XDM Sequences was incorrectly returning an empty sequence. This could lead to insufficient results being returned by an XQuery.
  • Fixed another problem with uploading zero length binary files via. the XML:DB Remote API.
  • Fixed a number of issues with the LDAP Security Realm:
    1. Ensure the authenticated LDAP context is reused.
    2. Always close and dispose of any LDAP context that we create.
    3. Fixed encoding of CN and DN names during LDAP searches.
  • Fixed an issue where the XQuery function file:serialize could use the incorrect character encoding depending on which platform eXist-db was being executed on.
  • Fixed a comparison problem with node equality in the DOM API exposed via. the XML:DB Local API.
  • Fixed a java.nio.file.Path issue when loading eXist-db's conf.xml file from inside a classpath Jar file.
  • Removed unnecessary error level logging of the XQuery fn:error function.
  • Fixed an issue with the error message for restoring permissions; Now the entire resource URI is shown.
  • Fixed an initialise/reset issue with Internal Module XQuery variables. This fixed a regression introduced in eXist-db 3.5.0.
  • Fixed a JavaEE dependency runtime issue with Java 11.
  • Downloading of XAR files during the eXist-db build process is now more descriptive.
• Incorporated from 4.3.0:
  • Fixed an issue where in-memory documents used in XQuery Update insert expressions caused an NPE (NullPointerException).
  • Fixed an issue where XQuery Error Codes were not correctly reported under some circumstances.
  • Fixed an issue with restoring binary files of zero bytes via the XML-RPC and XML:DB Remote API.
  • Fixed a signing issue with running eXist-db from the installer under Java 10.
  • Fixed an issue when constructing in-memory documents with namespaces via SAX parsers.
  • Fixed an issue with namespaces when parsing external documents to in-memory documents.
  • Fixed an issue with namespaces when merging in-memory documents.
  • Fixed a NPE when calling map:get for a non-existent key/value map pair.
  • Fixed a NPE in fn:data.
  • Fixes a NPE when converting empty sequences.
• Incorporated from 4.2.1:
  • Fixed an NPE with XQuery Update insert preceding with attributes. Closes #1761 and #1939.
  • Only attributes which are considered boolean in HTML5 have their values omitted. Closes #777. Thanks to Bert Willems from FontoXML for this fix.
  • Fixed an issue with the XQuery function inspect:module-functions, which was previously throwing a NPE. Closes #1927.
  • Fixed an issue with restoring Compressed (Zip) database backups. Closes #1913.

Bug fixes

• Fixed a regression introduced in eXist-db 4.3.0, where the type conversion of non-empty XDM Sequences was incorrectly returning an empty sequence. This could lead to insufficient results being returned by an XQuery.
• Reverted Apache Xerces 2.12.0 to 2.11.0. This fixes a regression introduced in eXist-db 4.3.0, whereby Xerces 2.12.0 proved to be incompatible with betteForm. Apache Xerces 2.12.0 is available in eXist-db 5.0.0-SNAPSHOT, and will be available from eXist-db 5.0.0-RC2 onwards.
• Fixed another problem with uploading zero length binary files via. the XML:DB Remote API.
• Fixed a number of issues with the LDAP Security Realm:
  1. Ensure the authenticated LDAP context is reused.
  2. Always close and dispose of any LDAP context that we create.
  3. Fixed encoding of CN and DN names during LDAP searches.
• Fixed an issue where the XQuery function file:serialize could use the incorrect character encoding depending on which platform eXist-db was being executed on.
• Fixed a comparison problem with node equality in the DOM API exposed via. the XML:DB Local API.
• Fixed a java.nio.file.Path issue when loading eXist-db's conf.xml file from inside a classpath Jar file.
• Removed unnecessary error level logging of the XQuery fn:error function.
• Fixed an issue with the error message for restoring permissions; Now the entire resource URI is shown.
• Fixed an initialise/reset issue with Internal Module XQuery variables. This fixed a regression introduced in eXist-db 3.5.0.
• Fixed a JavaEE dependency runtime issue with Java 11.
• Downloading of XAR files during the eXist-db build process is now more descriptive.

Backwards Compatibility

• eXist-db v4.3.1 is backwards binary-compatible as far as eXist-db v3.0, but not with earlier versions. Users who are upgrading should always consult the Upgrading Guide in the documentation.
• NOTE: The version of Dashboard that was installed with eXist-db 3.6.1 (or earlier) is incompatible with eXist-db 4.0.0 and newer. If you plan to migrate your entire database to eXist-db 4.3.1, you MUST take one of the following steps to allow Dashboard to work after the upgrade:
  1. If you have not yet installed eXist-db 4.3.1, open Dashboard > Package Manager, and upgrade Dashboard to 0.4.10, or run this script in eXide or the Java Admin Client: repo:install-and-deploy("http://exist-db.org/apps dashboard", "http://demo.exist-db.org/exist/apps/public-repo/modules/find.xql"). Then you may safely install eXist-db 4.3.1 and use Dashboard.
  2. If you install eXist-db 4.3.1 before upgrading Dashboard, run this script in eXide or the Java Admin Client: repo:install-and-deploy("http://exist-db.org/apps/dashboard", "http://demo.exist-db.org/exist/apps/public-repo/modules/find.xql"). Then you may use Dashboard.

Downloading This Version

• eXist-db v4.3.1 is available for download from GitHub.
• Docker images are available from EvolvedBinary's DockerHub.
• Maven artifacts are available from our mvn-repo.
• Mac users of the Homebrew package repository may acquire eXist 4.3.1 directly from there.

Features

• Upgraded to Apache Xerces 2.12.0. eXist-db now includes XML Schema 1.1 support.
• Improved the Remote XML:DB API "networking error" messages to be more descriptive.
• Test errors are now summarised in XQSuite XML output.

Bug fixes

• Fixed an issue where in-memory documents used in XQuery Update insert expressions caused an NPE (NullPointerException).
• Fixed an issue where XQuery Error Codes were not correctly reported under some circumstances.
• Fixed an issue with restoring binary files of zero bytes via the XML-RPC and XML:DB Remote API.
• Fixed a signing issue with running eXist-db from the installer under Java 10.
• Fixed an issue when constructing in-memory documents with namespaces via SAX parsers.
• Fixed an issue with namespaces when parsing external documents to in-memory documents.
• Fixed an issue with namespaces when merging in-memory documents.
• Fixed a NPE when calling map:get for a non-existent key/value map pair.
• Fixed a NPE in fn:data.
• Fixes a NPE when converting empty sequences.

Backwards Compatibility

• eXist-db v4.3.0 is backwards binary-compatible as far as eXist-db v3.0, but not with earlier versions. Users who are upgrading should always consult the [Upgrading Guide](http://exist-db.org/exist/apps/doc/upgrading.xml) in the documentation.
• NOTE: The version of Dashboard that was installed with eXist-db
• 6.1 (or earlier) is incompatible with eXist-db 4.0.0 and newer. If you plan to migrate your entire database to eXist-db 4.3.0, you
• MUST take one of the following steps to allow Dashboard to work after the upgrade:
  1. If you have not yet installed eXist-db 4.3.0, open Dashboard > Package Manager, and upgrade Dashboard to 0.4.10, or run this script in eXide or the Java Admin Client: repo:install-and-deploy("http://exist-db.org/apps/dashboard", "http://demo.exist-db.org/exist/apps/public-repo/modules/find.xql"). Then you may safely install eXist-db 4.3.0 and use Dashboard.
  2. If you install eXist-db 4.3.0 before upgrading Dashboard, run this script in eXide or the Java Admin Client: repo:install-and-deploy("http://exist-db.org/apps/dashboard", "http://demo.exist-db.org/exist/apps/public-repo/modules/find.xql"). Then you may use Dashboard.

Downloading This Version

• eXist-db v4.3.0 is available for download from GitHub.
• Docker images are available from EvolvedBinary's DockerHub.
• Maven artifacts are available from our mvn-repo.
• Mac users of the Homebrew package repository may acquire eXist 4.3.0 directly from there.

## v5.0.0-RC1 - June 9, 2018

We are very excited to announce the first Release Candidate (RC) for eXist-db 5.0.0.

NOTE: A Release Candidate is not recommended for production use. We have tested the release extensively, and we now invite all users to report both their positive and negative experiences with it. As always please make sure you have frequent and correct backups of your database.

The core improvements to eXist-db's locking, concurrency, and transactions in 5.0.0-RC1 represent a huge amount of work contributed by Evolved Binary. For in-depth information on these changes, see Evolved Binary's technical reports: Locking and Cache Improvements for eXist-db and Asymmetrical Locking for eXist-db.

In eXist-db 5.0.0-RC1, all locking interactions have been redesigned and reimplemented from the ground up; a number of deadlock paths have been removed; and many operations have been redesigned to be thread-safe. The result is that eXist-db should exhibit better responsiveness under concurrent user operations. For example, because collection locks are now multi-read capable, re-indexing the database no longer blocks access to the collection being re-indexed. Users should notice improved responsiveness during such operations.

5.0.0-RC1 also contains some security fixes and bug fixes that necessitated API changes and thus were not suitable for the existing 4.x.x line.

### Backwards Compatibility

• eXist-db v4.2.1 is backwards binary-compatible as far as v3.0, but not with earlier versions. Users who are upgrading should always consult the Upgrading Guide in the documentation.
• NOTE: The version of Dashboard that was installed with eXist-db 3.6.1 (or earlier) is incompatible with eXist-db 4.0.0 and newer. If you plan to migrate your entire database to eXist-db 4.2.1, you MUST take one of the following steps to allow Dashboard to work after the upgrade:
  1. If you have not yet installed eXist-db 4.2.1, open Dashboard > Package Manager, and upgrade Dashboard to 0.4.10, or run this script in eXide or the Java Admin Client: repo:install-and-deploy("http://exist-db.org/apps/dashboard", "http://demo.exist-db.org/exist/apps/public-repo/modules/find.xql"). Then you may safely install eXist-db 4.2.1 and use Dashboard.
  2. If you install eXist-db 4.2.1 before upgrading Dashboard, run this script in eXide or the Java Admin Client: repo:install-and-deploy("http://exist-db.org/apps/dashboard", "http://demo.exist-db.org/exist/apps/public-repo/modules/find.xql"). Then you may use Dashboard.