Hi, Otho. Do you have some solutions for then problem. I get the exceptions now, and I don't want to use the ApplicationContext Service to get bean by name.
Otho wrote: > > Since Spring beans are not exposed anymore as services I get exceptions > like > > > Error obtaining injected value for field org.example.user.Login.dao: > Spring > context contains 2 beans assignable to type org.example.dao.Dao: dao, > daoImpl. > > I couldn't find anything in the docs about injecting by name. And the > proposes workaround for non singletons with injecting ApplicationContext > and > then get the bean by name/id works, but is a bit awkward in cases like > this. > > Is there some other possibility? If not, is support for injection by name > planned in the future without the 5.0 compatibility mode? > > -- View this message in context: http://www.nabble.com/T-5.1-How-to-inject-Spring-beans-by-name--tp22934788p23690308.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
