Elemental 6.11.0 and 7.7.0 have been released

We are delighted to announce that Elemental versions 6.11.0 and 7.7.0 have just been released.

We were a little behind schedule with these two releases (i.e. release every two months). By way of excuse, whilst the Change Log for the releases looks small, there were a huge amount of internal changes made to improve things; we modified in excess of 500 files.

These releases include a small number of important bug fixes, a new Java API for executing an XQuery whilst ensuring all resources are reclaimed, support for the XML Calabash 3 XProc Processor, and a few performance improvements that reduce resource contention when executing XQuery. The main highlights are that:

There is a new API for executing XQuery and ensuring all resources used in execution are cleaned up. All XQuery execution in Elemental now goes through this API; through that change we have also removed a number of resource leaks (inherited from eXist-db) associated with executing XQuery code. This also now fully enables our support for XQuery execution via Elemental in XML Calabash 3 XProc Processor.

Previously (inherited from eXist-db) when executing an XQuery which is stored in the database, the XQuery document would be locked for the duration of its compilation and execution. Now, in Elemental, the XQuery document is only locked during compilation. This greatly reduces contention on XQuery documents, and fixes some concurrency issues that were encountered when editing XQuery documents from oXygen XML Editor or eXide.

The releases are available from:

• https://github.com/evolvedbinary/elemental/releases/tag/elemental-6.11.0
• https://github.com/evolvedbinary/elemental/releases/tag/elemental-7.7.0

Features

1. There is a new API for executing XQuery and ensuring all resources used in execution are cleaned up. All XQuery execution in Elemental now goes through this API; through that change we have also removed a number of resource leaks associated with executing XQuery code. This also now fully enables our support for XQuery execution via Elemental in XML Calabash 3 XProc Processor - #264
   
   

2.  

   When executing an XQuery which is stored in the database, the XQuery document is now only locked during compilation. This greatly reduces contention on XQuery documents, and fixes some concurrency issues that were encountered when editing XQuery documents from oXygen XML Editor or eXide - #229

3. Added a new system:get-main-module-load-path() XPath function to restore compatibility with TEI-Publisher - #231

Bug Fixes

1. Restore support for oXygen XML Editor - #215
   
   
2. Ensure that the Base URI is always a valid URI; relative XSLT imports from XSLT documents stored in the database now resolve correctly - #219
   
   
3. Ensure that the Base URI of in-memory documents is set correctly - #204
   
   
4. Set the HTTP Response Content-Type when writing JSON results from the REST API - #212
   
   
5. Improve the resolution and loading of configuration files on Windows platforms - #216

Backwards Compatibility

• Elemental 6.11.0 is 100% backwards compatible with Elemental 6.10.10(and eXist-db 6.4.0), and it should be a simple drop-in replacement for any user. Like Elemental 6.10.0 it requires Java 8.
• Elemental 7.7.0 is 100% backwards compatible with Elemental 7.6.0, and it should be a simple drop-in replacement for any user. Like Elemental 7.6.0 it requires Java 21.

Further information and downloads can be found here: https://github.com/evolvedbinary/elemental/releases