[jira] [Closed] (TAP5-627) Allow injection of named spring beans

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-627.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Allow injection of named spring beans
> -------------------------------------
>
>                 Key: TAP5-627
>                 URL: https://issues.apache.org/jira/browse/TAP5-627
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-spring
>    Affects Versions: 5.1.0.2
>            Reporter: Paul Field
>              Labels: bulk-close-candidate
>
> Since 5.1 now handles Spring beans through the master object provider, it is (I think) impossible to specify spring beans by name, which is a pain when you have multiple spring beans implementing the same interface.
> Could the Spring Object Provider take notice of an annotation that specifies the bean name, please?  (e.g. @Service or @Id)
> It would be particularly nice if the same annotation specified the names of Tapestry IOC services *and* spring beans, so that if we decide to move services from Spring into Tapestry IOC we don't need to change any other code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)