Transactions spanning database and server upload etc.

Hi Colin,

But that's the thing - I have a Service object called FormManager, which makes calls to the database using my FormDAO which uses HibernateTemplate, and in the same method (addForm()) also calls the server API using my FormsetDAO (on the Server it's called a FormSet) which will be managed by my Server transaction stuff.

So, what do I set as the Transaction manager for the FormManger service object when I wrap it as TransactionProxyFactoryBean? At the moment it's the HibernateTransactionManager, but that's without the server stuff...

Many thanks,

David

Presumably you are going to add your own code to synchronize to the existing database transactions (as per the previous entries), but that can still all be handled through the one transaction manager, HibernateTransactionManager in this case. The fact that this transaction manager is Hibernate aware and creates a session to bind to the current thread/tx on entry does not impede synchronizing other aspect to it as well...

Everything that needs to be transactional needs to be wrapped with a proxy which is hooked up to this transaction manager. When it comes to your server stuff which needs to synched in, you have to do it in a fashion similar to the way the existing classes which do this kind of thing (like SessionFactoryUtils) do it.

Regards,


Regards,

Colin,

thanks! That was one of the missing pieces!! Things are progressing much better now...

Just a quick qu:

Is there any reason that SpringSessionSynchronization (inner class in SessionFactoryUtils) receives both the SessionHolder and the SessionFactory - can't it just get the SessionHolder using the SessionFactory via TransactionSynchronizationManager?

cheers,

David

I too have a similar need. In our current system, we "simulate" XA txns via a composite TransactionManager (of our own design), in which Oracle, JMS, and other instances get registered. Since our TransactionManager is not really XA (it just does its best using single phase commit) the registered sub-managers are assigned a priority. For example, JMS is always the lowest priority so that messages are only sent to clients if all else succeeds. While this leaves some holes, it is very fast compared to XA.

So, my question: From your posts and my browsing, I gather that there is no concept of a composite TransactionManager in spring. And that TransactionSynchronizationManager is used to register resources that will be called back by AbstractPlatoformTransactionManager.

But we would like to use the predefined spring Hibernate and JMS txn managers (and get rid of our own). So I'm a bit confused as to how to proceed in recreating our "poor-mans" XA using spring.

Quote:

---

Originally Posted by hay7777

Just a quick qu:

Is there any reason that SpringSessionSynchronization (inner class in SessionFactoryUtils) receives both the SessionHolder and the SessionFactory - can't it just get the SessionHolder using the SessionFactory via TransactionSynchronizationManager?
David

---

Consider the resume method for example, where it needs to rebind the session holder with the session factory as the key. That's at least one place it needs both. Once it has it for that, it may as well use it in a number of other places directly (it's cleaner), even if it could theoretically get it from the synchronization manager.

Barry,

There's no composite in the sense of xa and 2 phase commit. But to tell you the truth, short of having real 2pc in your various datasources, I don't really understand what your 'composite' transaction manager is doing that you couldn't do by just using one of the Spring TMs (HibernateTransactionManager or JTATransactionManager probably make the most sense), and synchronizing all your resources. The issue is that ultimately, to get 2pc equivalent functionality, as per the main topic of this thead, you're going to have to manually back out some changes in the case of a commit failure...