You can certainly use a TransactionInterceptor (and HiveUtils has one of these), but it won't be automatically added to your HiveMind-managed services like it will in Spring.
-----Original Message----- From: Andreas Bulling [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Bulling Sent: Monday, February 20, 2006 10:00 AM To: Tapestry users Subject: Re: [OT] Re: Best practice - Integration Hibernate/Tapestry Hi Richard, first, thanks for your answer! | I have succesfully used HiveMind and Spring together with Tapestry and | Hibernate. I used Spring for this HibernateTemplate and transactional | support, so just defined DAOs in Spring. I used HiveMind to define all | other services, and using the HiveMind-Spring connector library, it was | simple to inject the Spring DAOs into the HiveMind services that needed | them. Uh, that sounds even more complex to me :( | However, I am not completely happy with this as a solution, as it is | unnecessarily complex, and I have not solved how to inject HiveMind | services into Spring so there is a natural disconnect there. With | hivetrans, it is likely that I will drop Spring altogether and just use | HiveMind. As you don't appear to want HibernateTemplate, I would suggest | just sticking with HiveMind, which is a little harder initially to pick | up than Spring, but IMO a more productive solution once you grok it. | Particularly as HiveMind is integral to Tapestry. Well, at least I _think_ that I don't need HibernateTemplates... What's the good thing about them besides "clear application layering" as mentioned in the spring reference documentation? And what about the interceptor stuff and session/transaction handling? Is this also possible with Hivemind/do drop-in solutions already exist? Thanks! Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
