Hi Lorenzo, Why are you developing a new component instead of using a idempotentConsumer (http://camel.apache.org/idempotent-consumer.html) in the camel which will take care about the data already processed ?
Regards, Charles On Thu, Aug 30, 2012 at 11:35 AM, lorenzo <laurent.deco...@sungard.com>wrote: > Hello there, > > I am writing a custom camel component which essentially has to record what > it has sent successfully so that it does not resend the same piece of info > twice. > > Surely this involves a transactional behaviour. The data is read from a DB > (JDBC) and is sent to a JMS queue. All good in terms of transactional > capabilities. > > Now, where do I start and end my transaction ? I was thinking to use the > wireTap EIP and make the whole thing transactional. I am therefore creating > a new point of inflexion in my route. > > Now I realize that reading the data, making note that the data has been > read, and publishing it is one same atomic action, it does not make sense > to > have one part without the others. So I think it is better to encapsulate > all > this in one small chunk. > > Anyway, I am not sure what I am suggesting makes any sense, I am open to > suggestions. > > Kind Regards > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Transaction-design-for-a-custom-compononent-tp5718361.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Charles Moulliard Apache Committer / Sr. Pr. Consultant at FuseSource.com Twitter : @cmoulliard Blog : http://cmoulliard.blogspot.com
