Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 27 Oct 2015 10:58:28 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12908192.1445943500000.71233.1445943508008@Atlassian.JIRA>
In-Reply-To: <JIRA.12908192.1445943500000@Atlassian.JIRA>
References: <JIRA.12908192.1445943500000@Atlassian.JIRA>
 <JIRA.12908192.1445943500725@arcas>
Subject: [jira] [Created] (CAMEL-9261) Claim Check EIP - DataStore spi and
 out of the box stores
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Claus Ibsen created CAMEL-9261:
----------------------------------

             Summary: Claim Check EIP - DataStore spi and out of the box stores
                 Key: CAMEL-9261
                 URL: https://issues.apache.org/jira/browse/CAMEL-9261
             Project: Camel
          Issue Type: New Feature
          Components: camel-core, eip
            Reporter: Claus Ibsen
             Fix For: Future


We should consider a ClaimCheckRepository API (or potentially allow to reuse aggregate repository) and add into the DSL to make it easy to store / claim.

A blog about this
http://www.javaprocess.com/2015/10/distributed-services-with-apache-camel-part2.html

And the eip
http://camel.apache.org/claim-check.html

Likely the aggregator repository is the best suited to reuse/extend from as its to store with a key -> exchange. And have apis to remove as well.

But we need to give it a bit more thought. The idea is for the implementations to make them reusable so we do not have to implement this again for JDBC, hazelcast and what else we have today for repositories.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)