Skip to content

@Configuration imported via @ImportResource is not processed [SPR-11723] #16345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Apr 23, 2014 · 3 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Apr 23, 2014

Dave Syer opened SPR-11723 and commented

Similar but different to #16056 (and more surprising and irritating to users). Originally raised via Spring Boot at spring-projects/spring-boot#710.


Affects: 4.0.3

Issue Links:

2 votes, 6 watchers

@spring-projects-issues
Copy link
Collaborator Author

Dave Syer commented

Test case: spring-attic/spring-framework-issues#73

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Aug 12, 2014

Juergen Hoeller commented

Finally addressed through reiterating the configuration class detection algorithm until no new configuration bean definitions are being found in the registry, similar to how we do it for BeanDefinitionRegistryPostProcessors (#15258).

Juergen

@spring-projects-issues
Copy link
Collaborator Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants