[
https://issues.apache.org/jira/browse/TAP5-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-627:
------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
