[
https://issues.apache.org/jira/browse/CONFIGURATION-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611924#comment-13611924
]
Yanlin Ye commented on CONFIGURATION-535:
-----------------------------------------
Thanks for your response. I've read CONFIGURATION-180 for a second time (I
read it before I created this one). Although I also created a cache for the
properties, it was not my intention. Instead, it was just the result of
meeting my need of property access even with database connection errors. That
is, I just want the properties (for error reporting) no matter what. A
preloaded and refresh-on-access cache was just my (imperfect but working) way
to fulfill my requirement.
Actually, the suggestions (especially #3) in the last reply to
CONFIGURATION-180 or the plan mentioned in the blocking issue CONFIGURATION-311
will perfectly serve my need. If they are going to be implemented in version 2
as planned, I guess you don't have to do anything to my request, for we can
simply wait for version 2.
> Add getters for the initial parameters of DatabaseConfiguration
> ---------------------------------------------------------------
>
> Key: CONFIGURATION-535
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-535
> 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: http://www.atlassian.com/software/jira
