Well, of course I'm going to say to use HiveMind, but use the Spring stuff inside HiveMind (like I do). That is, use HiveMind to wire everything together. If you *really* want to use the @Transactional annotations, I suppose I could be coerced into writing some code that supports it (cost, 1 case of Goose Island Honkers Ale...kidding of course...somewhat). The trick is that you'd have to have the @Transactional annotations on your service interface.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Hans L Sent: Monday, April 24, 2006 3:31 PM To: tapestry-user@jakarta.apache.org Subject: tapestry, hivemind, spring Hi, I'm wondering if anyone (James?) can give me some advice on configuring tapestry service points with spring. I am using spring to build my sessionFactory and autoproxy my DAO beans to use [annotation-based] declarative transactions. I'd really like to implement James' EntityPropertyPersistenceStrategy; however, it looks like the only way to configure Tapestry is via Hivemind services. So, I think my only options are: 1- modify the hivemodule.xml and EntityPropertyPersistenceStrategy to use DefaultSpringBeanFactoryHolder to allow me to pull my sessionFactory and hibernateService beans from Spring application context. 2- switch everything over to using HiveMind. (I suppose I lose ability to use @Transactional declarative transactions ... I'm also not entirely sure what the analogy is to using Spring's dataSource beans and sessionFactory.) Am I missing other option(s)? For example, is there a way to set Tapestry configuration points from Spring? I understand that philosophically HiveMind and Spring are fairly different -- and, at least on paper, I do like the distributed nature of the HiveMind approach, but Spring has a large selection of existing integration tools and far more extensive documentation. Thanks again - Hans --------------------------------------------------------------------- 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]
