Skip to content

Release 1.0.0

Jump to bottom
Dave Reynolds edited this page Jul 15, 2015 · 7 revisions

This is a major milestone release for the registry-core package and includes breaking changes from earlier 0.x releases.

The released war is available from registry-core-1.0.0.war

Changes

  • CSV. Support for CSV format for both read and update, uses a custom CSV format.
  • Batch registration. Allows registration of multiple entities in a single payload, no longer necessary to have explicit RegisterItems in the case where there is more than one entity.
  • Edit. A new edit operation that supports both registration of new entries and patching of existing entries in a single payload. In combination with CSV support this provides for convenient round-trip editing of a register using spreadsheet tools (may need to use Libre/Open office rather than Excel, some Excel versions are fragile handling CSVs).
  • Delete. Real delete operation which removes a register tree from the registry completely.
  • Import/export. New import and export operations for a register tree (as a n-quad dump). Allows selective backup/restore of register tree and brute force replication.
  • Custom life-cycle. Support for partial customization of status life-cycle.
  • Successor. Addition of reg:successor (inverse of reg:predecessor) and support and checking that successor is set when setting status to superseded.
  • Text indexing. The text indexing to support the search operation is now implemented using JenaText from Apache Jena - previously it had been a custom implementation. This gives better long term support and means that text index lookup and be included in SPARQL queries. There may be a modest performance impact from this since the prior custom implementation played games with "near real time" indexing and batching of updates. If that proves to be a problem then contributing to JenaText rather than maintaining and independent indexing solution would be the preferred route forwards.
  • Other. Various other bug fixes and improvements, together with updated base libraries including Jena (2.13.0).

Configuration (breaking change)

This release has switched to a maintained version of the base configuration library ("appbase" instead of "serverbase"). This uses a component configuration approach based on Apache Beanutils and inspired by Apache Shiro. The configuration syntax is slightly different and prior app.conf files will not work unmodified. See General configuration.

UI and configuration repository

A new repository registry-config-base provides a default standard setup for the registry UI and bootstrap configuration.

Deployment-specific configurations such as registry-deploy-env2 now use registry-config-base as an upstream source to simplify propagation of template file changes and bug fixes.

Clone this wiki locally