On Fri, Jun 29, 2012 at 4:33 PM, Igor Drobiazko
igor.drobia...@gmail.com wrote:
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
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
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
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
