{"id":17530,"date":"2013-09-24T01:00:55","date_gmt":"2013-09-23T22:00:55","guid":{"rendered":"http:\/\/www.javacodegeeks.com\/?p=17530"},"modified":"2013-09-23T12:38:49","modified_gmt":"2013-09-23T09:38:49","slug":"injecting-spring-beans-into-non-managed-objects","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2013\/09\/injecting-spring-beans-into-non-managed-objects.html","title":{"rendered":"Injecting Spring beans into non-managed objects"},"content":{"rendered":"

Advantages coming from dependency injection can be addicting. It’s a lot easier to configure application structure using injections than doing all resolutions manually. It’s hard to resign from it when we have some non-managed classes that are instantiated outside of the container – for example being part of other frameworks like Vaadin<\/a> UI components or JPA entities. The latter are especially important when we’re using Domain Driven Design<\/a>. During DDD training ran by Slawek Sobotka<\/a>\u00a0we were talking about options to remove “bad coupling” from aggregate factories. I’m sure you’ll admit, that it’s better to have generic mechanism able to “energize” objects by dependencies defined by e.g. @Inject annotation than inject all necessary dependencies into particular factory and then pass them into object by constructor, builder or simple setters.<\/p>\n

Spring framework brings us two different solutions to achieve such requirement. I’ll now describe them both of them. Let’s start with with simpler one.<\/p>\n

<\/a>It’s especially powerful when we’ve case such as generic repository, mentioned earlier aggregate factory, or even any other factory just ensuring that we have only few places in our code where will instantiate objects outside of the container. In this case we can make use of AutowireCapableBeanFactory<\/a>\u00a0class. In particular we will be interested in two methods:<\/p>\n