Contact Free trial Login

Object Store Connector Release Notes - Mule 3

Support Category: Select

The Anypoint Connector for Object Store enables you to manipulate object stores in Mule 3 apps. This connector provides access to default in-memory, custom, and persistent object stores.

2.2.4

February 11, 2020

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

None.

Fixed Issues

Object Store now correctly releases resources after the Dispose Store operation. (CONN-4804)

Known Issues

None.

2.2.3

July 24, 2019

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

  • None.

Fixed Issues

  • Users weren’t able to install this connector. This issue has been fixed.

Known Issues

None.

2.2.2

July 23, 2019

Note: This release was replaced with version 2.2.3 of the connector.

2.2.1

June 13, 2019

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

None.

Fixed Issues

  • Default value functionality fixed.

Known Issues

None.

2.2.0

June 8, 2018

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

None.

Fixed Issues

Warning: This version behaves differently than previous versions when dealing with object store references and partitions. Previously, when setting an object store reference, the partition name parameter was ignored. It is now used, and the connector tries to create that partition and use it.

  • Dispose Store operation on CloudHub - The Dispose Store operation would not work under CloudHub with Object Store v2. This has been fixed.

  • Partitionable stores - Previously, the partition parameter was ignored when the user provided an Object Store reference. This was changed, and the connector will attempt to create the partition in the given Object Store instance, if it is partitionable.

Known Issues

  • _defaultUserObjectStore in standalone runtime - It does not allow creating partitions. If you set it as an objectstore-ref, make sure not to set a partition name.

2.1.1

March 2, 2018

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

None.

Fixed Issues

  • ClassCastException when target property is defined - The retrieve method used to fail with a ClassCastException when a "target" property was defined and the payload sent to the connector was non-serializable. This is no longer the case.

Known Issues

None.

2.1.0

February 3, 2017

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

  • 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.

Fixed Issues

None.

Known Issues

None.

2.0.1

June 21, 2016

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

None.

Fixed Issues

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

Known Issues

None.

2.0.0

May 18, 2016

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

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

Fixed Issues

  • 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.

Known Issues

None.

1.3.3

August 3, 2015

Compatibility

Software Version

Mule

3.6, 3.7, 3.8, 3.9

ObjectStore

2013

Java

7

Anypoint Studio

5 and 6

Features

Added two new operations: retrieveWithLock and retrieveStore.

Fixed Issues

  • 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.

Known Issues

None.

Was this article helpful?

💙 Thanks for your feedback!

Leave feedback…