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 2025/12/28 11:16:00 UTC

[jira] [Resolved] (CAMEL-9261) Claim Check EIP - DataStore spi and out of the box stores

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

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

You can use a custom aggregation repository where you can persist if you need.

There has not been any ask for this for a long time so lets close

> 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
>            Priority: Major
>             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
(v8.20.10#820010)