Currently, when injecting Spring autowired dependencies via @SpringBean,
Wicket's Spring integration does 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.
Regards
Ben
--
*Ben Hutchison
Senior Developer
* Level 2 476 St Kilda Road Melbourne VIC 3004
T 613 8807 5252 | F 613 8807 5203 | M 0423 879 534 |
www.ibsglobalweb.com <http://www.ibsglobalweb.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
