camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Karlsen <davidkarl...@gmail.com>
Subject Re: File-component not transacted?
Date Thu, 29 Mar 2012 22:00:51 GMT
Either that or commons. Transactions from apache. I have a spring
transactionmanager abstraction of that again on github - could be
interesting or not.
Den 29. mars 2012 22:16 skrev "Reuben Garrett" <reubengarrett@gmail.com>
følgende:

> yes, i remember filesystem operations in java tending towards the "lowest
> common denominator" (e.g. locks are advisory [1]).
>
> maybe idempotency [2] in flows downstream of the file consumption could
> help achieve the desired behaviour?
>
> [1]:
> http://docs.oracle.com/javase/6/docs/api/java/nio/channels/FileLock.html
> [2]: http://camel.apache.org/idempotent-consumer.html
>
> ~ Reuben
>
> On Thu, Mar 29, 2012 at 14:38, Christian Müller <
> christian.mueller@gmail.com
> > wrote:
>
> > The file protocol per se doesn't support transactions. In Camel we try to
> > mimic the transactional behavior with error compensation if something
> went
> > wrong. But if we hit an error after we committed the JMS messages (which
> > supports transactions), we cannot do anything else.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message