DeltaXML Sync Release Notes


Table of Contents

Release 2.4.2
Release 2.4.1
Release 2.4
Release 2.3
Release 2.2
Release 2.1
Release 2.0
Release 1.2
Release 1.1.1
Release 1.1
Release 1.0
Release 0.9
Release 0.8
Release 0.7

Release 2.4.2

28th March 2008

  • Enhancement: incorporated DeltaXMLCore optimisations into DeltaXMLSync

Release 2.4.1

12th January 2008

  • Bug fix: When using a ParameterizedFilter in the PipelinedSynchronizer.setInputFilters(List) methods an erroneous UnsupportedFilterListMemberException would be thrown. This was a fault in the obsfucation/release procedure which has been corrected.

Release 2.4

14th December 2007

  • Bug fix: Simplified activation/license management implementation. The previous, 2.3, release increase our exposure to a number of bugs and missing features in various JVM implementations. This release provides a replacement implementation while preserving the activation mechanism/model and the named-user, professional-server and enterprise license types.
  • Enhancement: Support for using the enhanced matchers found in recent core releases. This includes changes so that while attributeValues appear as PCDATA in the unidelta representation they are treated as attributes and thus ignored when matching using the enchanched matchers.
  • Enhancement: Support for units of granularity in concurrent edit.
  • Bug fix: certain combinations of attributes prevented the dxu:attributes element being this first child of its parent element. This caused invalid unidelta output and further problems in the concurrent-edit pipelines.

Release 2.3

23rd August 2007

  • Bug fix: Resolved classloading and bean decoding issues when sync.jar is used in conjunction with other software (eg: Alfresco) which also uses the TrueLicense APIs.
  • Enhancement: Added support for URIResolvers to PipelinedSynchronizer and DXPConfiguration

Release 2.2

24th April 2007

  • Enhancement: New licensing model that requires activation using license files prior to running

Release 2.1

22nd January 2007

  • Added the Concurrent Edit ruleset/format, and appropriate DXP configuration support for associated pipeline
  • Updated to Saxon 8.8.0.4 to avoid a duplicate startDocument SAX event.

Release 2.0

4th December 2006

  • New underlying rule-driven implementation
  • Use of Java filters for larger capacity and higher performance
  • Support for DXP configuration and pipeline model as used in DeltaXML Core
  • Separate packages for pipelined and JAXP interfaces

Release 1.2

16th April 2004

  • Updates to documentation to remove TODO notes, correct some URLs and generally complete
  • Changed examples to use address book data with pipeline code for keying/dekeying
  • Removed unnecessary/unused failure types from the FailureType enumeration (easier to add in future than remove them).

Release 1.1.1

6th April 2004

  • Better handling of namespace prefixes in output, should prevent xmlns="" type output.

  • Removed extra trailing space in attribute conflict warnings.

Release 1.1

30th March 2004

  • Bug fixes to normalize-space and sync-word-by-word-in.xsl

  • Depends on DeltaXML Core API 2.8

Release 1.0

January 2004

New internal pipeline structure for better support of textual/markup data

Release 0.9

  • SAX subpackage moved back into parent

  • simple package renamed direct

  • New feature support (WBW, normalize, hide...)

  • Uses new Core error codes

Release 0.8

Extends evaluation expiry

Release 0.7

Changed the namespace string or URI used to represent annotation and conflicts used internally and in result files.

The namespace for annotation, typically used with the dxann: prefix (used internally and should not be visible in result files) changes from: http://www.deltaxml.com/ns/annotated-for-3-way-merge to: http://www.deltaxml.com/ns/sync-annotation

The namespace used for representing conflicts and tpyically used with the dxwarn: prefix changes from: http://www.deltaxml.com/ns/warning-for-3-way-merge to: http://www.deltaxml.com/ns/sync-warning

The names of elements and attributes used to represent conflict information in results files have changed, the following table lists the changes, using the namespace prefixes mentioned above:

Old nameNew name
dxwarn:modifiedOldDeletedNewdxwarn:modifiedEdit1DeletedEdit2
dxwarn:modifiedNewDeletedOlddxwarn:modifiedEdit2DeletedEdit1
dxwarn:old-attributesdxwarn:edit1-attributes
dxwarn:new-attributesdxwarn:edit2-attributes
dxwarn:PCDATAolddxwarn:PCDATAedit1