You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/12/13 09:44:01 UTC

[jira] [Resolved] (CAMEL-12041) Introduce ConcurrentMapIdempotentRepository and MapIdempotentRepository

     [ https://issues.apache.org/jira/browse/CAMEL-12041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-12041.
---------------------------------
    Resolution: Won't Fix

> Introduce ConcurrentMapIdempotentRepository and MapIdempotentRepository
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-12041
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12041
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.20.1
>            Reporter: Marc Carter
>            Priority: Trivial
>
> In order to more generically plug in third-party data fabrics, Camel should directly support the ConcurrentMap interface.
> 1 Add an explicit ConcurrentMapIdempotentRepository (which does away with synchronized blocks around the backing map) 
> 2 Factor our MapIdempotentRepository from MemoryIdempotentRepository (being based on a Map _interface_ doesn't make it "memory" - only the default LRUCache impls are definitively "memory")
> 3 Make some sense of the tests around this EIP



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)