Object Store Connector Release Notes - Mule 3

None.

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

Default value functionality fixed.

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.

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

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.

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.

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

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

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.

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.