Nav

Object Store Connector Release Notes (Mule 3)

February 2017

The Anypoint Connector for the Mule Object Store enables the manipulation of object stores within Mule. It provides access to default in-memory, custom, and persistent object stores.

MuleSoft maintains this connector under the lhttps://www.mulesoft.com/legal/versioning-back-support-policy#anypoint-connectors[Select] support policy.

Compatibility

The Object Store connector is compatible with:

Application/Service Version

Mule Runtime

3.6.x or higher

ObjectStore

2013

Java

1.7.0_x

Anypoint Studio

5.x or higher

Version 2.1.0 - February 3, 2017

  • New operation: Dispose store: Removes an object store partition. Before, the only way to remove an object store partition was by calling the disposePartition function of the ObjectStoreManager inside a Java custom component.

Version 2.1.0 - Fixes

None.

Version 2.1.0 - Known Issues

None.

Version 2.0.1 - June 21, 2016

Version 2.0.1 Features

None.

Version 2.0.1 Fixes

  • When using a persistent object store, all entries were getting deleted, in error, at shutdown and re-deployment.

Version 2.0.1 Known Issues

None.

Version 2.0.0 - May 18, 2016

  • All processors are executed inside a lock, thus providing consistency and avoiding data loss or corruption when working with transactions or concurrency, for example.

Version 2.0.0 Fixes

  • Processor retrieveWithLock was removed as a consequence of the lock implementation described above.

  • Updated connector support category to Select.

  • Added user manual describing the usage of the connector.

Version 2.0.0 Known Issues

None.

Version 1.3.3 - August 03, 2015

Version 1.3.3 Features

Added two new operations: retrieveWithLock and retrieveStore.

Version 1.3.3 Fixes

  • Previously, the retrieve operation did not modify the payload when the target property was set. This has been fixed.

  • Fixed an error that caused the connector to not validate its global parameters.

Version 1.3.3 Known Issues

None.