AnnotationConfigApplicationContext doesn't process @Configuration classes scanned by component scan. [SPR-10984]

[spring-projects-issues]

Andruschuk Borislav opened SPR-10984 and commented

Let's consider the following case:

@Configuration
@ImportResource("some.xml")
public class SomeClass { ... }

in some.xml:

<context:component-scan base-package="com.somepackage"/>

in com.somepackage there's class:

@Configuration
public class OtherClass {

   @Bean(name="SomeNewBean")
   public Object getSomeBean(){ ... }
}

If AnnotationConfigApplicationContext is used against first configuration class only (SomeClass) I assume last configuration class (OtherClass) should be processed as well. However the bean defined inside last configuration class doesn't exist in application context after initialization (refresh).

Some investigation showed that ConfigurationClassPostProcessor is not invoked for OtherClass therefore any annotations inside class never get processed.

---

Affects: 3.0 GA

Issue Links:

• INT-3207 Ensure Annotation Configuration support for Infrastructure components ("is depended on by")
• @Configuration imported via @ImportResource is not processed [SPR-11723] #16345 @Configuration imported via @ImportResource is not processed ("duplicates")

3 votes, 6 watchers

[spring-projects-issues]

Phil Webb commented

Unfortunately this is a limitation of the current @Configuration implementation. If you use the @ComponentScan annotation, any found @Configuration beans will be processed, beans found from XML loaded via @ImportResource will not.

Are you able to use the @ComponentScan annotation instead of <context:component-scan>?

[spring-projects-issues]

Andruschuk Borislav commented

Unfortunately I cannot use @ComponentScan in that specific case because of project structure: we create different types of ApplicationContext in different applications we combine from set of our modules.

[spring-projects-issues]

Phil Webb commented

Another option might be to always start from XML, even for the @Configuration classes. You should be able to include <context:annotation-config> and <bean class="SomeClass".

[spring-projects-issues]

Andruschuk Borislav commented

Our workaround for now is just use ClassPathXmlApplication context instead of AnnotationConfigApplicationContext, it doesn't have such issue and processes all @Configuration classes correctly.

[spring-projects-issues]

Artem Bilan commented

Hi, Phil!

We catched the same issue in the SI, when we was going to simplify our life using @Configuration.
Can you take a look into our PR: spring-projects/spring-integration#932?
Pay attention on IntegrationConfigurationClassPostProcessor.
Maybe it can help somehow to fix this issue.

Thanks

[spring-projects-issues]

Daniel Fritsi commented

Hi,
I know this has been fixed, but unfortunately we are still on Spring 4.0 and we cannot update any time soon, and there's a use case where we have to use an AnnotationConfigApplicationContext. Is it somehow possible to import a spring xml with AnnotationConfigApplicationContext so that if I have a Configuration class written in Java and I'm using it in the xml like

<bean class="com.my.small.app.MySpringConfig" />

it gets properly processed?