You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/30 13:35:11 UTC

[jira] [Updated] (TAP5-1179) Exclude non-autowire candidate beans from being injected when using @Inject

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

Jochen Kemnade updated TAP5-1179:
---------------------------------


This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

> Exclude non-autowire candidate beans from being injected when using @Inject
> ---------------------------------------------------------------------------
>
>                 Key: TAP5-1179
>                 URL: https://issues.apache.org/jira/browse/TAP5-1179
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-spring
>            Reporter: Dustin Woods
>            Priority: Minor
>
> It would be nice for Tapestry-Spring to follow the same behavior as Spring when injecting beans based on type.
> Spring JIRA Issue
> http://jira.springframework.org/browse/SPR-7120?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> Spring JIRA Issue Fix
> https://fisheye.springsource.org/browse/spring-framework/trunk/org.springframework.beans/src/main/java/org/springframework/beans/factory/support/DefaultListableBeanFactory.java?r1=3287&r2=



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