[
https://issues.apache.org/jira/browse/WICKET-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2495.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
this is a pretty bad idea. beans get renamed, fields get refactored/renamed.
all of these cause silent breakages. this is the bane of anyone who has ever
worked with seam2 and other frameworks where injection by name was the only way.
> @SpringBean should use field name for default bean name
> -------------------------------------------------------
>
> Key: WICKET-2495
> URL: https://issues.apache.org/jira/browse/WICKET-2495
> Project: Wicket
> Issue Type: Wish
> Affects Versions: 1.3.4
> Reporter: Ittay Dror
> Assignee: Igor Vaynberg
> Attachments: WICKET-2495.patch, wicket-spring-jpa-legup-2495.tgz
>
>
> When using @SpringBean, the bean is found either by name if the annotation
> specifies one or by field type.
> I'd like to suggest that if the annotation does not specify a name, then the
> field name is used as the bean name and only if a bean with that name is not
> found, is the type used.
> This is because I think most of the time people use a field names the same as
> the bean name (while there can be several beans of the same type)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
