So far @javax.inject.Inject and @javax.inject.Named annotations are "replacements" for @Inject and @InjectService. Everything what is possible with Tapestry built-in annotations is also possible with JSR-330 annotations, there are some semantic differences though. Please read here:
http://blog.tapestry5.de/index.php/2011/01/17/javax-inject-inject-support-in-tapestry/ I think @Named annotation should allow to get a Spring bean by its id. That's why I asked for the reason why Spring beans can't be injected with @InjectService annotation, which is a sibling of @Named. On Wed, Feb 2, 2011 at 3:33 PM, Alex Kotchnev <akoch...@gmail.com> wrote: > Ulrich, > do the standard @Inject and @Named annotations only expose the existing > functionality (e.g. injecting T5 services by type and name) or would they > support injecting spring beans by ID (e.g. using @Named) ? > > Regards, > > Alex K > > On Wed, Feb 2, 2011 at 9:17 AM, Ulrich Stärk <u...@spielviel.de> wrote: > > > https://issues.apache.org/jira/browse/TAP5-1385 > > > > > > On 02.02.2011 13:39, Werner Keil wrote: > > > >> At least Spring 3 is using the Java standard @Inject by now, T5.1 > didn't. > >> Not sure, if 5.2 has finally done so, but if not, there lie some > >> incompatibilities... > >> > >> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > -- Best regards, Igor Drobiazko http://tapestry5.de
