Fall release

Highlights:

• upgrade to ActiveMQ 5.14.0
• added function to start/stop globally the ReplicationTrigger
• improved logging in ReplicationTrigger : all operations are now logged in INFO level
• enabled connection pooling by default (commons-pool2 dependency)

xquery version "3.1";

import module namespace replication="http://exist-db.org/xquery/replication" 
              at "java:org.exist.jms.xquery.ReplicationModule"; 


replication:enableReplication(true())

(exact function name under discussion-has been changed in 0.9.12)

Detailed changes: v0.9.10...v0.9.11

Repair of sync() function

Minor update: the new sync() function now correctly reads the collection configuration

Detailed changes: v0.9.9...v0.9.10

Featured: Synchronize metadata

This pre-release is an important step for the extension. Some highlights:

• document metadata is now finally replicated in the correct way
• created time/lastmodified time is now included too
• added replication:sync() and replication:sync-metadata() functions
• document ownership now based on... the name of the owner, in stead of the group name.
• upgrade version of activemq to 5.13.3

xquery version "3.1";

import module namespace replication="http://exist-db.org/xquery/replication" 
              at "java:org.exist.jms.xquery.ReplicationModule"; 

(: collection.xconf in /db/system/conf/db/replicated/ collection :)
replication:sync('/db/replicated/document.xml'),
replication:sync('/db/replicated/collection/'),
replication:sync-metadata('/db/replicated/document.xml'),
replication:sync-metadata('/db/replicated/collection/')

Known issue (or not):
Currently investigating #77

Detailed changes: v0.9.8...v0.9.9

Important replication fix

Replication messages were not explicitly acknowledged by the code, cause messages not te be removed from the broker.

This issue has been overlooked for a long time; very important though!

Logging has been improved as wel: each replication event is now logged, with limited info in INFO mode, a lot more on DEBUG

Detailed changes: v0.9.7...v0.9.8

Stability improvements

Some issues were found:

• an unknown mime type would stop replication of a document
• log levels and log texts were misleading

publisher 1
2016-04-25 18:38:30,373 [eXistThread-461450] ERROR (Sender.java [createMessageFromExistMessageItem]:395) - No payload for replication

is not an error, just a message

publisher 2
"Collection %s already exists" should not be logged as an error

receiver
2016-04-25 18:17:05,469 [ActiveMQ Session Task-1] INFO  (ReplicationTrigger.java [afterDeleteDocument]:228) - Blocked replication trigger for /db/apps/blabla1.xml: was received by replication extension.l

should not reported as an error, could be a WARN; restyled text to "Prevented re-replication of '%s'"

Detailed changes: v0.9.6...v0.9.7

Bump to AMQ 5.13.2

• Applied static code checks
• Use Java8 lambdas where possible (and there it makes sense)
• Better resource management (ARM)
• Documentation has been improved too, all example URLs point to localhost now

eXist-db 3.0 RC2 compatibility

This version is compatible with eXistdb 3.0 RC2 ("3.0.2").
Update to ActiveMQ 5.13.0

Bugfixes and improvements

This release contains quite some fixes and improvements

• made compatible with recent exist3 changes
• update to activemq 5.12.0
• setting username/password on broker connection works again
• java8 optimization
• fix: prevent re-replication
• use copycontext for xquery to prevent xquery context issues

❗ v0.9.4 is compatible with eXist-db 3.x ❗

Detailed changes: v0.9.2...v0.9.4

Updates and bugfixes

• Authentication and Authorization on the broker connection is functional again.
• Fix: prevent re-replication
• Fix: use copycontext in functions

❗ v0.9.3 is compatible with eXist-db 2.2 ❗

Detailed changes: v0.9.1...v0.9.3

Make compatible with eXist v3.0 (v2.3)

Wrapup of all work done to make the extension work with the latest exist-db version

v0.9.1...v0.9.2