I had tried this. It doesn't seem to be supported. From the docs for tapestry-ioc:
SpringBean ObjectProvider (tapestry-spring) Attempts to resolve a Spring bean purely by object type (Spring qualifiers are not supported). If no beans are assignable to the type, then processing continues. If exactly one is assignable, it is used as the injection value. If more than one bean is assignable, it is an error (and a list of matching beans names will be part of the thrown exception). I came across a description of how to do it in a less ugly fashion (sorry, I can't find a reference to it, but it might very well be the same solution originally given). I had problems getting it to work, whatever it was, and I needed to move forward. Hence my workaround. I do miss the ability to inject by id. JB On Mon, Jul 26, 2010 at 12:14 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, 26 Jul 2010 12:00:50 -0300, Christian Koller < > christian.kol...@net-m.ch> wrote: > > Is there a better solution than this here: >> >> http://stackoverflow.com/questions/2684171/tapestry-5-and-spring-beans-with-same-interface >> > > What about using @InjectService("serviceId")? > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Jonathan Barker ITStrategic
