Download

1. eXist-db versions

Release 1.4 will be our next production quality release. It is currently available as a release candidate. Among other things, this release improves eXist's XQuery processing thanks to a better and more robust handling of in memory documents. It features faster and customizable full text indexing by transparently integrating Lucene into the XQuery engine. eXist now also provides a lightweight URL rewriting and MVC framework (which in part replaces Cocoon), along with support for XProc, XForms and many new XQuery extension modules.

The final 1.4 release will replace the current 1.2 series as stable branch. Release 1.5 becomes the new bleeding edge development release. New features will be added to this release only.

Note

Even release numbers (1.0.x, 1.2.x) indicate 'production' releases whose code has been tested for a longer time but are frozen except for important bug fixes. Odd releases (1.1.x, 1.3.x) are created from the active branch of development and contain all features and bug fixes.

2. Downloads

For information concerning upgrades from previous versions, see our Upgrade Guide.

2.1. Release Candidate 1.4 (Codename: Eindhoven)

1.4 (Stable Release Candidate)
eXist-setup-1.4rc-rev10028.jar Installer based on IzPack. Includes source. Run with java -jar eXist-1.4rc-rev10028.jar
eXist-setup-1.4rc-rev10028.exe Installer based on IzPack. Includes source. Required for MS Vista.
We no longer distribute a .war package as we would like to encourage new users to start with the stand alone distribution. Running eXist within an isolated environment helps to identify issues and avoid unnecessary problems. However, experienced users can always repackage the standard distribution. It only takes seconds.
eXist as Cocoon block
The release candidate of eXist still includes Cocoon 2.1.11. However, this will be dropped from the final version. As before, we would like to ship an "eXist as Cocoon block" build, but this requires an update of our build scripts to Cocoon 2.2.0. If you have Cocoon 2.2.0 working with eXist, please consider to give us a helping hand.

2.2. Stable Release (Codename: Rennes)

1.2.5 (Current release)
eXist-setup-1.2.6-rev9165.jar Installer based on IzPack. Includes source. Run with java -jar eXist-setup-1.2.6-rev9165.jar
eXist-setup-1.2.6-rev9165.exe Installer based on IzPack. Includes source. Required for MS Vista.
eXist-1.2.6-rev9165.war Web application archive, ready to be installed into an existing servlet-engine like Tomcat or Jetty.
eXist as Cocoon block
The standard distribution already ships with Cocoon. However, this version is a bit older and offers only a subset of the available Cocoon modules (called "blocks" in Cocoon). If you work a lot with Cocoon, you might prefer to have eXist integrated into full Cocoon build. The installer-based distribution contains build scripts to set up eXist as a block in Cocoon. Please refer to the documentation. As a service to Cocoon users, we also provide a pre-compiled Cocoon 2.1.11 below:
cocoon-2.1.11-with-eXist-1.2.6.war This is Cocoon version 2.1.11 build with standard options and eXist 1.2 as a block. You should find eXist in http://my-server:port/cocoon/samples/blocks/exist/.

3. Important Notes

3.1. Java versions

eXist-db version 1.2.x requires at least java 1.4.2. Starting with eXist-db version 1.4, at least Java5 is required. The database has been implemented and tested with the Java implementation of Sun. Implementations of other vendors will probably work but have not been tested as extensively.

3.2. Endorsed library

eXist-db heavily depends on the Apache Xerces2 parser, Apache Xalan-Java XSLT processor and the Apache XML Commons Resolver libraries. When eXist-db is installed in a servlet container like tomcat, these jar files must be made available to eXist via the java endorsed feature.

3.3. Tomcat

Due to some restrictions of Apache Tomcat the validation functions do not fully work on stored documents (using the xmldb:exist:///-type URLs - Note the three slashes).

By default Apache Tomcat is started with a limited HeapSize. This heapsize must be increased to have optimal performance and to prevent "Out of Memory" errors.

September 2009
Dannes Wessels
dizzzz@exist-db.org