Even Tapernate won't consider spring beans for autowiring. Spring beans aren't "services" in the HiveMind world. That's not to say that you can't expose them as services, but you have to explicitly set up a service declaration and use the SpringLookupFactory as your implementation factory. Tapestry 4.x has built-in (used to be an external module called tapestry-autowire) support for autowiring of HiveMind services. All you have to do is declare an abstract "getter" of the type you need (as long as there's exactly one service in the registry that has that service interface, which is usually the case) on your component/page class.
On 8/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > have a look at tapernate (http://www.carmanconsulting.com/tapernate/) > > > -----Original Message----- > > From: Ari Miller [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 31, 2007 12:35 AM > > To: [email protected] > > Subject: tapestry-spring autowiring > > > > > > We are using hivemind 1.1. > > Many of our services are autowired with our existing > > persistence services. > > We want to switch to injecting in our persistence services > > from Spring, to take advantage of container managed transactions. > > I can inject in spring beans using the tapestry-spring > > functionality, but autowiring doesn't seem to be available. > > Is there an established pattern for also considering Spring > > beans when autowiring within hivemind? > > > > P.S. > > I am aware of hivetranse, but would prefer to use Spring for > > this purpose. > > -- > > View this message in context: > > http://www.nabble.com/tapestry-spring-autowiring-tf4357304.htm > l#a12417539 > > Sent from the Hivemind - User mailing list archive at Nabble.com. > > > > >
