search

spring-projects / spring-framework

Spring Framework
https://spring.io/projects/spring-framework
Apache License 2.0
56.47k stars 38.09k forks source link

Addition of DatabaseOverrideConfigurer [SPR-1556] #6254

Closed spring-projects-issues closed 12 years ago

spring-projects-issues commented 18 years ago

Jason Vinson opened SPR-1556 and commented

I am working on a project that requires a gui to configure our system and we are currently using PropertyPlaceholderConfigurer to set up our beans. We'd like to make them read/write configurable for the user in a reasonably easy manner and I feel that the most obvious approach is to use the database.

I've written a first draft of a DatabaseOverrideConfigurer, as a subclass of PropertyOverrideConfigurer, which works wonderfully so far. I'm sure it could use a little polish, but I'm attaching it to see if it makes sense to include as a configuration module.

Attachments:

2 votes, 2 watchers

spring-projects-issues commented 18 years ago

Jason Vinson commented

The implementation

spring-projects-issues commented 18 years ago

Jason Vinson commented

A fairly basic test case

spring-projects-issues commented 15 years ago

Paul Austin commented

I would like to raise this enhancement request again and have attached some example code I've been using for the last few years to do this. I'm now getting to the point where I'm recommending this approach to be used on several hundred projects for a provincial Government so would prefer this was a standard piece of funtionality.

The configurator is configured using a data source, table name, key column name and value column name. Other than that its similar to the PropertyOverrideConfigurator. I may have added some changes to support map properties.

\<bean id="databaseConfigurator" class="com.revolsys.ui.web.config.DatabasePropertyOverrideConfigurer"> \ \ \ \ \config_properties\ \ \ \property_name\ \ \ \property_value\ \ \ \true\ \ \

spring-projects-issues commented 12 years ago

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.