Exporting / Importing beans across ApplicationContexts [SPR-4034]

[spring-projects-issues]

Eberhard Wolff opened SPR-4034 and commented

Spring JavaConfig allows to only export beans that are created by a public method. This allows for nice modularization of applications by using one JavaConfig class for each component and export the interface of the module only. Such a feature would be nice for XML based configuration as well.
I can imagine it as some special way of handling <import >. An alternative would be an enhacement for the SingletonBeanFactory locator that allows you to define the beans that should be exported in the Spring configuration that includes the BeanFactories that might be accessed. Maybe there are other good possibilities as well.

---

Issue Links:

• Support @Bean method visibility [SPR-7170] #11829 Support @Bean method visibility

1 votes, 2 watchers

[spring-projects-issues]

Rossen Stoyanchev commented

This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug.

There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it.

If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description.

We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.