Your understanding is correct. However I would like to add something Whereas if the scope is defined as session for the bean, if a user makes a request for a web page more than once, then on every request same bean would be returned. I would change it as “Whereas if the scope is defined … Read more
First, and most important – all Spring beans are managed – they “live” inside a container, called “application context”. Second, each application has an entry point to that context. Web applications have a Servlet, JSF uses a el-resolver, etc. Also, there is a place where the application context is bootstrapped and all beans – autowired. … Read more
Stumbled upon this question while searching exactly this. Finally I found out that it works in Spring 3.1 using @EnableWebMVC in conjunction with WebMvcConfigurerAdapter. Simple Example: @Configuration @EnableWebMvc @ComponentScan(basePackages=”webapp.base.package”) public class WebApplicationConfig extends WebMvcConfigurerAdapter { @Override public void addInterceptors(InterceptorRegistry registry) { registry.addInterceptor(new LoggerInterceptor()); } }
Found what the issue was. Copy/paste from comments: Are you sure you have <context:property-placeholder> in the same application context as your MyClass bean (not in the parent context)? – axtavt You’re right. I moved <context:property-placeholder> from the context defined by the ContextLoaderListener to the servlet context. Now my values get parsed. Thanks a lot! – … Read more
I finally figured it out… Sometimes, asking a question can give you a better approach to your problems :p The problem is I was linking the validators to the list before they were mocked. The validators was then null and no reference could be updated when the MockitAnnotations.initMocks(this) was called. Moreover, to avoid iterator problems … Read more
You can obtain your bean from the context by name dynamically using a BeanFactory: @Service public class Doer { @Autowired BeanFactory beans; public void doSomething(Case case){ CaseService service = beans.getBean(case.getCountryCode(), CaseService.class) service.doSomething(case); } } A side note. Using something like country code as bean name looks a bit odd. Add at least some prefix or … Read more
According to the Javadoc for Autowired, the annotation can be used on “a constructor, field, setter method or config method”. See the full documentation for more details. I personally prefer your first option (constructor injection), because the myDao field can be marked as final: @Controller public class MyControllear { private final MyDao myDao; @Autowired public … Read more
Here is an abstract FactoryBean implementation that does autowiring for you: public abstract class AbstractAutowiringFactoryBean<T> extends AbstractFactoryBean<T> implements ApplicationContextAware{ private ApplicationContext applicationContext; @Override public void setApplicationContext( final ApplicationContext applicationContext){ this.applicationContext = applicationContext; } @Override protected final T createInstance() throws Exception{ final T instance = doCreateInstance(); if(instance != null){ applicationContext .getAutowireCapableBeanFactory() .autowireBean(instance); } return instance; } … Read more
You can use @Qualifier to solve it. In your case you can make: @Bean(name=”fullSpot”) // Not mandatory. If not specified, it takes the method name i.e., “fullSpotField” as qualifier name. public FieldDescriptor fullSpotField() { FieldDescriptor ans = new FieldDescriptor(“full_spot”, String.class); return ans; } @Bean(“annotationIdSpot”) // Same as above comment. public FieldDescriptor annotationIdField() { FieldDescriptor ans … Read more
You can’t @Autowired a static field. But there is a tricky skill to deal with this: @Component public class StatisticLogger { private static Dao dao; @Autowired private Dao dao0; @PostConstruct private void initStaticDao () { dao = this.dao0; } } In one word, @Autowired a instance field, and assign the value to the static filed … Read more