Oliver Zeigermann <oliver.zeigermann <at> gmail.com> writes: > I do not think it should be too difficult, but what would be the real > benefit? The XA resource would store files locally only and a real 2 > phase commit does not work with the transactional file system.
I guess it is less a question of correct working than of integration. We have the need to run database updates, to execute Corba services and to modify the filesystem in transactions. From what I get (it's my first real contact with transactions not limited to databases) most of the TransactionManagers are based on Sun's JTA which is again based on the XA specification. So wrapping an existent transactional file access within a XAResource would be the simplest way to go, wouldn't it? > Anyway, if you have a decent running implementation of that and want > to donate it to the commons transaction project, I'd be my pleasure to > add it. Not yet :) Jörg > 2005/10/28, Joerg Heinicke <joerg.heinicke <at> gmx.de>: > > > I saw that commons transaction provides an implementation of transactional > > file access and an abstract implementation of > > javax.transaction.xa.XAResource. > > Now I wonder why these two are not combined and the transactional file > > access implementation does not exist as a XAResource. Is it so difficult, > > such a huge step forward? Or was there just nobody missing it? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
