Re: Multiple Spring beans of same interface
I think that the spring integration needs a bit of an overhaul. I seem to remember that tapestry does not ignore "abstract" springs bean which can also cause problems. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Multiple-Spring-beans-of-same-interface-tp5714183p5714190.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Multiple Spring beans of same interface
It's just not implemented, SpringModuleDef can check for @InjectService or @ServiceId and use getBean(name, type). Denis Jun 29, 2012 v 4:33 PM, Igor Drobiazko: > Can anyone remind me please why we don't support injection of Spring beans > by id when multiple beans of the same interface are available in the > application context? Was is any technical limitation? Can we change that? > This issue is annoying me again and again. > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > http://twitter.com/drobiazko - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Multiple Spring beans of same interface
Can anyone remind me please why we don't support injection of Spring beans by id when multiple beans of the same interface are available in the application context? Was is any technical limitation? Can we change that? This issue is annoying me again and again. -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko
