Please do. I might get rid of the HiveMind utils stuff. There's a bug in HiveMind that doesn't let me use my transaction interceptor with other interceptors. But, I can probably get around that by using CGLIB (not javassist) to generate the proxy classes.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Hans L Sent: Monday, April 24, 2006 4:05 PM To: tapestry-user@jakarta.apache.org Subject: Re: tapestry, hivemind, spring Thanks, James. I'll play around with this & if I get any transaction annotation support working I'll send it along. Hans James Carman wrote: > Well, you can find all the source code at the hivemind project at JavaForge. > Here's the source repositories for it all. > > http://www.carmanconsulting.com/svn/public/tapernate/trunk > http://svn.javaforge.com/svn/hivemind/spring-hibernate3/trunk > http://svn.javaforge.com/svn/hivemind/hivemind-utils/trunk > http://svn.javaforge.com/svn/hivemind/spring-transaction/trunk > > Note: To checkout from javaforge, you have to use anonymous/anon as the > username/password. > > > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Hans L > Sent: Monday, April 24, 2006 3:48 PM > To: tapestry-user@jakarta.apache.org > Subject: Re: tapestry, hivemind, spring > > Hi James, > > Actually, I'd be very happy to try my hand at writing support for the > @Transactional stuff, based on the Annotation support in Spring & the > TransactionInterceptorFactory in > com.javaforge.hivemind.spring.transaction package. I was trying to find > the source repository for some of the jars in tapernate (e.g. > spring-transaction.jar, spring-hibernate.jar), but was unable to do so. > I don't need @Transactional, though it is kinda nice :) > > I am leaning toward trying to do everything in HiveMind (but using > Spring, as you do); I just need to learn how to do the configuration > stuff -- and specifically what HiveMind provides for datasource > configuration, etc. > > Thanks- > Hans > > James Carman wrote: >> 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] >> >> > > > --------------------------------------------------------------------- > 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]
