[
https://issues.apache.org/jira/browse/WICKET-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871429#action_12871429
]
Hudson commented on WICKET-2365:
--------------------------------
Integrated in Apache Wicket 1.5.x #68 (See
[http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.5.x/68/])
WICKET-2365: support 'autowire-candidate' attribute
> Please support "autowire-candidate" attribute of a bean when injecting via
> @SpringBean
> --------------------------------------------------------------------------------------
>
> Key: WICKET-2365
> URL: https://issues.apache.org/jira/browse/WICKET-2365
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-spring
> Reporter: Ben Hutchison
> Assignee: Gerolf Seitz
> Priority: Minor
> Fix For: 1.5-M1
>
>
> Currently, when injecting Spring autowired dependencies via @SpringBean,
> Wicket's Spring integration does not take account of the optional
> "autowire-candidate" attribute of a bean. This attribute tells spring not to
> consider a bean during autowiring.
> Here's our use case where we discovered this limitation. Our app uses 2
> databases, a default database used by 95% of the code, and a reporting
> database used by the reports component. As a result we have 2
> SessionFactories in our context, and this breaks @SpringBean injection.
> It would be nice to cater for the 95% of code that doesn't use the reporting
> database, and use explicit names only for the other 5%. This seems to require
> the Wicket-Spring integration to understand the "autowire-candidate=false"
> attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
