Support of class ConfigurationSupport in Spring 3.0.x framework [SPR-6018]

[spring-projects-issues]

David Nemeshazy opened SPR-6018 and commented

We were using Spring 2.5.6 + Spring JavaConfig 1.0.0.M4 and are using the ConfigurationSupport class.

Now we are migrating toward Spring 3.0 (3.0.0.M4 currently) and don't have this class anymore.

We find this class very helpful and would like to have it part of Spring 3.0.x or have it in the next JavaConfig version that is based on Spring 3.0.x

---

Affects: 3.0 M4

Issue Links:

• Provide alternatives to using FactoryBean types within @Bean methods [SPR-7418] #12076 Provide alternatives to using FactoryBean types within @Bean methods ("is superseded by")

2 votes, 6 watchers

[spring-projects-issues]

Chris Beams commented

Hi David - could you provide a few of your most important use cases for ConfigurationSupport, i.e.: what are you unable to do at this point? There is a forthcoming release of JavaConfig that will build upon the core support in Spring 3.0, and it's likely that ConfigurationSupport or its equivalent will initially show up here.

[spring-projects-issues]

David Nemeshazy commented

Yes, of course.

We are using the following from ConfigurationSupport:

• getApplicationContext()
• getBean(Class<T> type)
• getObject(FactoryBean factoryBean, Class<T> requiredType)

Of course, we can implement BeanFactoryAware and ApplicationContextAware and do this ourselves, but it was much more convenient to simply extend ConfigurationSupport.

Thanks-

[spring-projects-issues]

Juergen Hoeller commented

As discussed previously, I don't think that we should be reintroducing ConfigurationSupport as we knew it. Revisiting what it did, most of it is first-class functionality in the BeanFactory in the meantime and can be used against a BeanFactory/ApplicationContext in a delegate fashion, with not much advantage from having such convenience methods in a base class. Note that you don't have to implement the *Aware interfaces anymore; you may also use a private @Autowired BeanFactory field...

If specific functionality is missing which you're nevertheless relying on in your concrete configuration classes even when refactoring them to delegate to BeanFactory / AutowireCapableBeanFactory / ApplicationContext, let us know. We'd consider adding it to BeanFactory or BeanFactoryUtils then.

Juergen

[spring-projects-issues]

Baruch Sadogursky commented

The only feature I missed from the original ConfigurationSupport was getObject(FactoryBean), and I hated to extend from it. So here is injectable version of ConfigurationSupport with getObject method - http://github.com/jbaruch/spring-java-configuration-support

[spring-projects-issues]

Chris Beams commented

See also #12076