camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Updated: (CAMEL-1679) InProgress repository
Date Mon, 08 Jun 2009 08:56:35 GMT


Claus Ibsen updated CAMEL-1679:

    Fix Version/s:     (was: 2.0.0)

We can wait till Camel 2.1 for this feature

> InProgress repository
> ---------------------
>                 Key: CAMEL-1679
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
> Adding a repository for registering in progress exchanges.
> The repository should be per camel context specific. It should contain a default memory
only repository, but support pluggable so end user can impl some other store if they like.
> It should support some notion of a key to identify whether a given message is already
in progress or not.
> The UnitOfWork can be used to register and de register in progress, so we ensure its
always done.
> We could by default just register the exchange id, and thus have a sort of current snapshot
of how many exchanges is currently in progress.
> Then we can let components override this behavior to use a key that is component specific
and has a meaning.
> For instance the file component can use the absolute file name as key to ensure that
it does not consume the same file while its already in progress.
> And the idempotent consumer EIP can use the correlation message id to ensure that it
also detects in progress messages.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message