v5.0.0-RC8 - July 31, 2019
The eighth Release Candidate (RC) for eXist-db 5.0.0 has been released.
eXist-db 5.0.0-RC8 builds atop eXist-db 5.0.0-RC7 with several new features and important bug fixes.
NOTE: This is likely the last Release Candidate before 5.0.0 is released. We kindly ask all users to test their applications on RC8, and report back any new issues since RC7. The testing window for RC8 is between 2 and 4 weeks, dependant on any issues reported by users. All being well, 5.0.0 final will be released by 31st Aug 2019.
- New Dashboard and Package Manager #2438.
- Improved the performance of the Lock Table #2591.
- Improved the performance of Lock Striping #2831.
- Optimized XMLString to reduce copying.
- Spatial Index is now available again #2601.
- Options can now be passed to
- A leading wildcard can now be used in
- Added the new function
ft:index-keys-for-fieldfor the Lucene Index to complement
util:index-keysfor field indexes.
- Added a
MetaAnalyzerfor the Lucene Index to allow different analyzers to be used per-field.
- Lucene Index definitions can now have a conditional expression provided in an
- Added experimental support for Faceting with the Lucene Index #2629.
- Added the
- Added the
- Added the
- Added the
- Added the
- Rewrote the Service Manager for Windows platforms.
- Docker images now use an Uber jar for easy deployment.
- New Jar Installer based on IzPack 5.
- Apache Ant 1.10.6
- Apache Commons Codec 1.12
- Apache Commons Compress 1.18
- Apache Commons Configuration 2.4
- Apache Commons Daemon 1.2.0
- Apache Commons File Upload 1.4
- Apache Commons HTTP Components 4.4.11
- Apache Commons Lang 3.9
- Apache Mina 2.1.2
- Apache Tika 1.20
- Bouncy Castle 1.5.1
- cglib 3.2.12
- Eclipse AspectJ 1.9.4
- Eclipse Jetty 9.4.18.v20190429
- EXPath Pkg 1.4.0
- EXPath HTTP Client 1.2.0
- EXPath Tools 0.3.0
- FasterXML UUID Generator 3.2.0
- IzPack 5.1.4
- Jackson 2.9.8
- JavaMail 1.6.3
- JLine 3.11.0
- MultiLock 1.0.1
- Quartz Scheduler 2.3.1
- RESTXQ 0.1.34
- RSyntaxTextArea 3.0.3
- Saxon HE 9.9.1-2
- SLF4j 1.7.26
- Added missing XML library dependencies for JDK 10+.
- Fixed non-spec compliant issues with
- Fixed a regression with XQuery Update's
insert followingexpression #2624.
- Removed a bad optimization affecting expressions like `/a/b//cd = 123]` [#2837.
fn:tokenizeis now case-sensitive by default #2742.
- Fixed an issue where the content of XML Comments was incorrectly escaped #2740.
- Reduced the memory use and increased performance of file transfers in the XML:DB API #2630.
- Reduced the memory use and computation when sorting.
- Reduced the memory use of Collections #2688.
- Fixed an issue whereby XQSuite was not reporting all test failures #2141.
- Fixed a memory leak with QNames during XML serialization #2537.
- Fixed memory leaks with the
- Fixed an issue whereby eXist-db might not start correctly if Journal Recovery was disabled #2539.
- Fixed a regression with overlapping transactions when deploying EXPath packages.
- Made the parsing of
util:serializeparameters conform with the function documentation.
- Ensure that all users have at least one Primary Group.
- Small fixes to the
- Fixed an issue with the Namespace Constructor when there is an empty prefix #2584.
- Removed custom buggy Hash Table implementations in favour of those in [fastUtil](http://fastutil fastutil.di.unimi.it/) #2588.
- Fixed Collection Locking when removing a Collection.
- Fixed the analysis of global variables when loading XQuery modules dynamically #2580.
- Fix an issue with replacing binary resources when owner/group differ from the active user #2595.
- Fixed purging of old zip backups #2609.
- Fixed a
LDAPRealmwhen searching for group members #2618.
- Corrected the order of arguments in
- Fixed the context sequence for XQuery higher-order-functions #2448.
- Fixed an
ArrayOutOfBoundsExceptionwhen querying documents with enclosed expressions and the
- Fixed a problem with Collation comparison on empty strings #2671.
- Fixed a problem with parallel sorting when using Collations #2669.
- Fixed an issue where descendent nodes were incorrectly indexed in the Lucene Index #2682.
- Fixed an issue with opening a Collection using a full XML:DB URL #2693.
- Avoid a
AutoDeploymentwhen dependencies are not available.
- Made sure that the Launcher correctly exits when requested #2730.
- Fixed an issue where previously replacing a document, would not remove all prior nodes which caused storage to constantly grow.
- Fixed a locking issue when deleting documents via WebDAV #2789.
- Fixed a regression with YAJSW support introduced by adding
- Fixed setting the admin password setting in the installer Jar.
- Fixed setting the data directory in the installer Jar.
- Fixed an issue whereby source locations were not correctly included in the installer Jar.
- Fixed JavaDoc syntax errors #2860.
We have removed the Java Web Application Archive (WAR) build of eXist-db. We no longer support running eXist-db inside a 3rd-party Servlet container such as Apache Tomcat. If you wish to operate eXist-db as a Server, you should instead run it server using the provided Jetty start-up scripts.
We have also removed a number of previously deprecated functions, modules, and extensions:
- Removed the draft syntax for the XQuery Map Constructor, i.e. `map = "y"` #2892.
- cache module:
cache:cache, caches are now created on demand.
- fn module:
fn:map, use the Map constructor instead.
fn:map-pairsfunction, you should instead use
- image module:
- map module:
map:newfunction, you should instead use the map constructor.
map:for-each-entry, you should instead use
- response module:
- sm module:
- util module:
util:catch, use XQuery 3.0's
util:parse, use XQuery 3.0's
util:serialize, use XQuery 3.0's
- validation module:
validation:validate, you should use the other more specific functions within this module.
validation:validate-report, you should use the other more specific functions within this module.
- xmldb module:
xmldb:change-user, instead use various task specific functions in the
- XQuery Context module.
- XQuery DateTime module. Consider using dtm.xqm instead.
- eXist-db's HTTP Client module. Use the EXPath HTTP Client module instead.
- eXist-db's XQuery FTP Client module. Use the EXPath FTP Client module instead.
- eXist-db's Math module. Use the XQuery 3.0 math functions instead.
- commands extension.
- fluent extension.
- Memcached extension.
- metadata extension.
- netedit extension.
- OAuth Security extension.
- OpenID Security extension.
- Scheduler extension.
- tomcat-realm extension.
- XMPP extension.
- XProcXQ extension. Consider using Calabash instead.
- xUnit extension.
New Build System
The build system for eXist-db was previously Apache Ant. With RC8 we have completed a complete migration of the build system to Apache Maven. Maven affords us a much more modular and rigorous, and flexible process, whilst reducing the maintenance burden that we experienced with Ant. We are now also able to easily publish artifacts to Maven Central for those eXist-db users that embed eXist-db within their own applications.
One major change, is that eXist-db can no longer be built "in-place" from a Git clone, instead building eXist-db now generates a distribution. It is recommended that all users working with the source code, should start with a fresh clone of eXist-db RC8, as its source footprint is not compatible with RC7 and before.
The Building eXist-db documentation page has been updated with the latest instructions for building eXist-db with Maven.
eXist-db 5.0.0-RC8 is binary compatible with eXist-db RC6 and RC7. Regardless, before upgrading to this version of eXist-db, it is strongly recommended to perform a full backup and restore. Users who are upgrading should always consult the Upgrading Guide in the documentation. For details of backwards compatibility with versions of eXist-db prior to 5.0.0-RC6, please see the Backwards Compatibility details of 5.0.0-RC6.
- NOTE: EXPath Apps shipped with previous version of eXist-db, are not guaranteed to be forwards compatible with RC8. As such when restoring a backup to RC8 you should at least exclude the following from your
If in doubt, you should consider excluding
/db/apps entrirely from your backup archive during the restore, and then subsequently installing the latest versions of the Apps you need via the Dashboard's Package Manager.
You can selectively restore single collections by unzipping the backup and pointing the restore to a single `contents.xml` file. This will only restore the corresponding collection.
An alternative approach would be:
- restore the entire backup, taking into account that the dashboard won’t be available afterwards
- open the Java admin client and issue an XQuery to update shared-resources and dashboard: