commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] [Commented] (CONFIGURATION-535) Add getters for the initial parameters of DatabaseConfiguration
Date Sat, 23 Mar 2013 16:15:16 GMT


Oliver Heger commented on CONFIGURATION-535:

Many thanks for your positive feedback!

Caching for DatabaseConfiguration is an interesting topic. There is alread a ticket for it
(CONFIGURATION-180), but no concrete work has been done in this direction. If you can contribute,
you are more than welcome!
> Add getters for the initial parameters of DatabaseConfiguration
> ---------------------------------------------------------------
>                 Key: CONFIGURATION-535
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Wish
>            Reporter: Yanlin Ye
>            Priority: Trivial
>              Labels: features
> We use database configuration to support a centralized location for configuration properties
common to some distributed components of our application, and it works great.  In order for
our application components to report issues (especially when we have database connection issues),
we extended database configuration to maintain a backup cache for all properties and update
the cache whenever a property is accessed.  This way, the cached properties can be used if
the properties cannot be loaded from the database.  The extension works as expected and can
report issues even if the database connection becomes not available.
> The only (minor) thing is that, when we extended DatabaseConfiguration, we had to maintain
another copy of the initial parameters such as table name, name/key/value columns, etc, because
DatabaseConfiguration does not provide access to them.  I was wondering whether or not the
following can be added to DatabaseConfiguration to make it easier to be extended.
> - Add getters for initialization parameters, and
> - Change private void close(Connection, Statement) to protected for reuse.
> Please ignore if you don't think the suggested changes can be useful to users.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message