[
https://issues.apache.org/jira/browse/WICKET-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2444.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
1.4.2
Assignee: Igor Vaynberg
> Internal Spring beans should be ignored
> ---------------------------------------
>
> Key: WICKET-2444
> URL: https://issues.apache.org/jira/browse/WICKET-2444
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-spring
> Affects Versions: 1.4.1
> Reporter: Ronald Tetsuo Miura
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.2, 1.5-M1
>
> Attachments: SpringBeanLocator.patch
>
>
> When looking up Spring beans by type (to inject into @SpringBean fields), the
> injector should ignore internal beans, like the ones generated by the
> <aop:scoped-proxy/> element at the configuration. In this case, the generated
> name always starts with 'scopedTarget.'.
> Other cases can be identified by the method
> 'BeanFactoryUtils.isFactoryDereference(name)'.
> These beans are created by the container to be used internally, so, shouldn't
> be considered for injection. The problem is, they usually have a mirror bean
> (which is the really injected by the container), so, when Wicket's injector
> tries to find it, it doesn't find unique beans of the type, forcing us to
> declare the bean name explicitly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
