Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.2.1
-
Fix Version/s: 3.2.0
-
Component/s: Core: Configuration
-
Labels:None
-
User impact:Medium
-
Effort points:0.5
-
Affects Docs:Yes
-
Similar Issues:None
Description
Currently, the idempotent-receiver-router XML element allows only a fixed set of object stores to be configured: in-memory-store and simple-text-file-store. You cannot, however, configure a custom obejct store.
Allow the following config:
<idempotent-receiver-router idExpression="#[header:Message-Id]"> <custom-object-store ref="xyz"/> or <custom-object-store class="xyz"/> <idempotent-receiver-router>
As workaround you can use the custom-inbound-router element and configure it though spring properties like this:
<custom-inbound-router class="org.mule.routing.inbound.IdempotentReceiver"> <spring:property name="idExpression" value="#[header:Message-Id]"/> <spring:property name="store" ref="DatabaseObjectStore"/> </custom-inbound-router>
(DatabaseObjectStore is a plain spring:bean in the config)
Issue Links
- blocks
-
MULE-5390
Provide an ehcache object store
-
The idempotent-message-filter available in Mule 3 suffers from the same limitation.