I recently committed a small change to UtilCache that allows us to
specify the properties file to use for cache settings. Currently, all cache settings for all components are contained in a single file - cache.properties - located in the base component. From my perspective, it would be nice to have each component use its own cache settings file, and the cache.properties file can be used for default settings and the base component only. What do you think? -- Adrian Crum Sandglass Software www.sandglass-software.com |
Thank you for the effort, I think this is a very good idea.
Also nice would be to allow overriding cache settings of another component, this means one wouldn't have to change OOTB files and there would be no need to maintain patch files either. This strategy could be extended to all files related to configuration (.properties or .xml). I've seen other open source projects which have such a strategy implemented, the only difference is that the OOTB configuration file to be extended has a suffix in its name (example: cache-ext.properties). -- Vyom On 25 August 2014 13:22, Adrian Crum <[hidden email]> wrote: > I recently committed a small change to UtilCache that allows us to specify > the properties file to use for cache settings. > > Currently, all cache settings for all components are contained in a single > file - cache.properties - located in the base component. > > From my perspective, it would be nice to have each component use its own > cache settings file, and the cache.properties file can be used for default > settings and the base component only. > > What do you think? > > -- > Adrian Crum > Sandglass Software > www.sandglass-software.com >
--
Vyom |
Being able to override properties settings would be nice and I tried
that once by modifying UtilProperties.java, but I ran into problems and then I ran out of free time before I could get it working. Adrian Crum Sandglass Software www.sandglass-software.com On 8/25/2014 11:27 AM, Vyom Jain wrote: > Thank you for the effort, I think this is a very good idea. > > Also nice would be to allow overriding cache settings of another component, > this means one wouldn't have to change OOTB files and there would be no > need to maintain patch files either. > > This strategy could be extended to all files related to configuration > (.properties or .xml). I've seen other open source projects which have such > a strategy implemented, the only difference is that the OOTB configuration > file to be extended has a suffix in its name (example: > cache-ext.properties). > > -- > Vyom > > > On 25 August 2014 13:22, Adrian Crum <[hidden email]> > wrote: > >> I recently committed a small change to UtilCache that allows us to specify >> the properties file to use for cache settings. >> >> Currently, all cache settings for all components are contained in a single >> file - cache.properties - located in the base component. >> >> From my perspective, it would be nice to have each component use its own >> cache settings file, and the cache.properties file can be used for default >> settings and the base component only. >> >> What do you think? >> >> -- >> Adrian Crum >> Sandglass Software >> www.sandglass-software.com >> > |
Administrator
|
In reply to this post by Adrian Crum-3
Le 25/08/2014 09:52, Adrian Crum a écrit :
> I recently committed a small change to UtilCache that allows us to specify the properties file to use for cache settings. > > Currently, all cache settings for all components are contained in a single file - cache.properties - located in the base component. > > From my perspective, it would be nice to have each component use its own cache settings file, and the cache.properties file can be used for default > settings and the base component only. > > What do you think? > As long as the default is the current cache.properties file this is fine with me Jacques |
Free forum by Nabble | Edit this page |