The autoproxy issue has already been brought up on the HiveMind developers list (by me). I really think we should try to implement this, as it really makes configuration easy when used in conjunction with annotations.
-----Original Message----- From: Jean-Francois Poilpret [mailto:[EMAIL PROTECTED] Sent: Monday, February 20, 2006 10:25 AM To: 'Tapestry users' Subject: RE: [OT] Re: Best practice - Integration Hibernate/Tapestry Hi all, Just one point (I talk as the author of HiveMind Utilities) I want to emphasize about auto-proxying: this is not a feature that HiveUtils can bring by itself, it belongs to the container (ie HiveMind). When/if HiveMind provides it, then HiveMind Utilities will provide it;-) Personnally (but I don't use Tapestry by itself, I just use HiveMind), I do not like much the idea of putting HiveMind + Spring together in the same application (and I would add that I don't like Spring XML config files: they are very obscure, compared with what you can do with HiveMind). It is right the HiveMind Utilities do not provide the same level of features to HiveMind that Spring provides to itself! And I don't believe it will one day. As far as I can say, Spring is becoming the elephant that it was supposed to kill, and I think it is harder and harder to get into it (but I don't want to start a war here, so please no flame;-)). Just my 2 Dongs (and that is really not much!) Jean-Francois -----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Monday, February 20, 2006 10:06 PM To: 'Tapestry users' Subject: RE: [OT] Re: Best practice - Integration Hibernate/Tapestry 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] --------------------------------------------------------------------- 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]
