From: atamar (A. F. <fo...@an...> - 2006-08-16 16:40:56
|
>From what I understand of your arch., client MDB calls your service which uses DAO to save an entity. If that's the case, I believe spring transaction synchronization is what is causing this issue. From the spring docs [/url]http://www.springframework.org/docs/api/org/springframework/transaction/jta/JtaTransactionManager.html[url] Quote: If JtaTransactionManager participates in an existing JTA transaction, e.g. from EJB CMT, synchronization will be triggered on finishing the nested transaction, before passing transaction control back to the J2EE container. (end of quote) Normally, Spring HibernateTemplate closes the session after each save() operation.Transaction sync is what allows spring to use the same Hibernate session for all operations within a transaction. However, with CMT the session is not being resued and hence Hibernate is complaining. However when you declare BMT, I believe you are not using programmatic transaction and hence spring is able to sync the transaction. Consequently you are not facing any issue. My 2 cents. Anand [/url] _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=15216#15216 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! |