You can do this using the autowireBean()
method of AutowireCapableBeanFactory
. You pass it an arbitrary object, and Spring will treat it like something it created itself, and will apply the various autowiring bits and pieces.
To get hold of the AutowireCapableBeanFactory
, just autowire that:
private @Autowired AutowireCapableBeanFactory beanFactory;
public void doStuff() {
MyBean obj = new MyBean();
beanFactory.autowireBean(obj);
// obj will now have its dependencies autowired.
}
You can also mark your MyClass with @Configurable annotation:
@Configurable
public class MyClass {
@Autowired private AnotherClass instance
}
Then at creation time it will automatically inject its dependencies. You also should have <context:spring-configured/>
in your application context xml.
Just got the same need and in my case it was already the logic inside non Spring manageable java class which had access to ApplicationContext
. Inspired by scaffman.
Solved by:
AutowireCapableBeanFactory factory = applicationContext.getAutowireCapableBeanFactory();
factory.autowireBean(manuallyCreatedInstance);
I wanted to share my solution that follows the @Configurable
approach as briefly
mentioned in @glaz666 answer because
Spring Neo4j & Aop starts
(which is irrelevant anyway)Spring Boot
is ready using @Configurable
approach (using ApplicationRunner
) I needed to follow the steps below in order to get it working
@Configurable(preConstruction = true, autowire = Autowire.BY_TYPE, dependencyCheck = false)
to be placed on top of your Bean
that is to be manually instantiated. In my case the Bean
that is to be manually instantiated have @Autowired
services hence, the props to above annotation. XXXApplicaiton.java
(or the file that is annotated with @SpringBootApplication
) with the @EnableSpringConfigured
and @EnableLoadTimeWeaving(aspectjWeaving=AspectJWeaving.ENABLED)
compile('org.springframework.boot:spring-boot-starter-aop')
and compile('org.springframework:spring-aspects:5.0.7.RELEASE')
Bean
that is annotated with @Configurable
anywhere and its dependencies should be autowired. *In regards to point #3 above, I am aware that the org.springframework.boot:spring-boot-starter-aop
transitively pulls the spring-aop
(as shown here mavencentral) but, in my case the Eclipse failed to resolve the @EnableSpringConfigured
annotations hence, why I explicitly added the spring-aop
dependency in addition to the starter. Should you face the same issue, just declare the dependency or go on adventure of figuring out
org.springframework.context.annotation.aspect.*
is not availableI used a different approach. I had spring loaded beans that I wanted to call from my extended classes of a third-party library that created its own threads.
I used approach I found here https://confluence.jaytaala.com/display/TKB/Super+simple+approach+to+accessing+Spring+beans+from+non-Spring+managed+classes+and+POJOs
In the non-managed class:
{
[...]
SomeBean bc = (SomeBean) SpringContext.getBean(SomeBean.class);
[...]
bc.someMethod(...)
}
And then as a helper class in the main application:
import org.springframework.beans.BeansException;
import org.springframework.context.ApplicationContext;
import org.springframework.context.ApplicationContextAware;
import org.springframework.stereotype.Component;
@Component
public class SpringContext implements ApplicationContextAware
{
private static ApplicationContext context;
public static <T extends Object> T getBean(Class<T> beanClass)
{
return context.getBean(beanClass);
}
@Override
public void setApplicationContext(ApplicationContext context) throws BeansException
{
SpringContext.context = context;
}
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With