You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Anatole Tresch (JIRA)" <ji...@apache.org> on 2015/06/15 11:58:00 UTC
[jira] [Resolved] (TAMAYA-35) Add new FilesPropertiesConfigProvider
[ https://issues.apache.org/jira/browse/TAMAYA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anatole Tresch resolved TAMAYA-35.
----------------------------------
Resolution: Won't Fix
Not clear for me: the paths suggested are classpath paths. Normally I would not expect a classpath to change during runtime, if so I would expect the classloader to be reloaded. Not doing so may leave the system in a inconsistent state. If the paths are more menat to be on the filesystem there ist the event module that implements the basics (even regardless the config comes from a filesystem or is updateable in other ways).
Given that I resolve this issue as of now.
> Add new FilesPropertiesConfigProvider
> -------------------------------------
>
> Key: TAMAYA-35
> URL: https://issues.apache.org/jira/browse/TAMAYA-35
> Project: Tamaya
> Issue Type: Improvement
> Components: Core
> Reporter: Otavio Goncalves de Santana
> Assignee: Anatole Tresch
>
> Add new provider that read the xml and properties files in below folders creates a new configuration.
> These files should be watched, once modified the configuration should be updated automatically.
> The folders will:
> * META-INF/cfg/
> * META-INF/config/
> * META-INF/tamaya
> This provider will have less priority than that already exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)