Late fixes

Renamed one trigger, updated documents. Rechecked replication feature.

Detailed change log via v0.9.0...v0.9.1

Refactoring

This release is a wrapup of work performed over a longer period of time. It is a preparation for the v1.0 release.

Detailed change log via 0.7.4...v0.9.0

Note:
The java package names have been changed, this will certainly influence existing applications. The restructuring was required to make the code more reliable. More details in the FAQ.

Compatibility

Make extension compatible again with exist 2.1 (confirmed)

Detailed change log via 0.7.2...0.7.4

UI: migrate to Bootstrap3

This release only contains a change in the UI; migrate to Bootstrap3

compatible with eXist-db v2.2

Detailed change log via 0.7.1...0.7.2

Continuing development

New feature:

• replication can now be started via a xquery function - which can be started via the XqueryStartupTrigger

Bugfix:

• removed mini-error report from managers screen. it was not usable.

Upgrade:

• update to ActiveMQ client 5.9.1

Build:

• Upgrade to new ivy update manager
• Cleaned warnings javadocs
• Cleaned warnings build

compatible with eXist-db v2.2

Detailed change log via 0.7...0.7.1

Restore compatibility with eXist-db 2.1

After the last stable version of eXist-db the internal API has been changed, on which the replication extension depends to prevent re-replication of data (#30). For eXist-db 2.1 this protection is now effectively switched off, which is not a problem when using the extension in a classic master-slave(s) configuration(s).

Note: older versions of the extension can cause database corruption (2.1 only) because an Error occurred in the eXist-db Trigger mechanism. Please upgrade ASAP to this version

The change hasn't been extensively tested due to timing issues.

Detailed change log via 0.6.1...0.7

Compatibility release

Make extension compatible with older 2.x releases

Detailed change log via 0.6...0.6.1

Bugfix release

Change log:

• Fixed issue where code in the 'callback function' was executed as 'guest' in stead of the user who registered the function
• improved some error texts
• improved reporting

Detailed change log via 0.5...0.6

XML Prague 2014 Preview release

A new development milestone:

• Implemented 'failover' mechanism where message is delivered to other receiver if original receiver was not able to process the message. See https://github.com/eXist-db/messaging-replication/tree/0.5/web/modules/testing
• Updated Web UI (receiver management)
• Updated documentation
• Replication function is functional again (sorry folks)
• Better error reporting/handling

Detailed change log via 0.4...0.5

Pre-release

The 0.4 version is the pre-release version of the extension.

Most important changes

• The receivers are now identified with an integer
• Improved error collection in the report
• Added a management UI to stop/start/close a receiver
• The build scripts have been improved