Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 74.125.44.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=cEU+EpwAw716j7np2NWleEhP4ZAIw/MiTkQbT8XA+5DA1Wt3/GTygCD4gO/9xQEaMa
         3aK114rQUPKmMhSJyNrp1mGIzYu0O3zlbCXyfzQYp8RDPbTd/Khk3/beI+gU/JWK9eaB
         +KpR3jn1YxR1eA8IoQfm4GxTez49aEeroYsfs=
Message-ID: <ec6e67fd0812010244x39ee53a3g59390ce1af014317@mail.gmail.com>
Date: Mon, 1 Dec 2008 10:44:28 +0000
From: "James Strachan" <james.strachan@gmail.com>
To: camel-dev@activemq.apache.org
Subject: Re: Deprecation of file consumer timestamp
In-Reply-To: <5380c69c0811290804i7292efbdi37c06cdd11021a5b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2748945d0811181057w760b0be7g4b23b372394b90b4@mail.gmail.com>
	 <49231A78.8070802@skynet.be>
	 <2748945d0811181904n2c9f5d37ufee7943d4f499495@mail.gmail.com>
	 <5380c69c0811190135o509a41ale3b0ff0c5fd149ee@mail.gmail.com>
	 <5380c69c0811190139i49a494cbh4f65df819d026a3a@mail.gmail.com>
	 <4923ED1A.1000301@skynet.be>
	 <ec6e67fd0811242224x681f43e9ne074349bf52cc2dc@mail.gmail.com>
	 <5380c69c0811290804i7292efbdi37c06cdd11021a5b@mail.gmail.com>

2008/11/29 Claus Ibsen <claus.ibsen@gmail.com>:
> Hi
>
> I am reworking the file component as the code needs to be polished to
> be ready for new feature requests by end users.
>
> Having my fingers on the keyboard and reworking the code I do think we
> should consider letting the idempotent consumer EIP pattern having a
> first class interface for consumers to implement to support idempotent
> right out-of-the-box. This is convenient for both the file and ftp
> consumers to avoid re-consuming already processed files.
>
> Then we could allow very easy URI configuration for the file consumer
> to enable the idempotent
> from("file://inbox?idempotent=true").to("bean:processOrder");

Great idea!

> So I am proposing to either
> a) add a new interface in org.apache.camel to cater for this
> b) move the existing interface MessageIdRepository to org.apache.camel
> c) option b but renaming the interface to a better name, IdempotentRepository
>
> Using the existing MessageIdRepository allows us to leverage existing
> implementations such as the JpaMessageIdRepository so we can support a
> persistent solution right out-of-the-box.

Sounds good - how about IdempotentRepository being in the camel.spi package?
-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/