[
https://issues.apache.org/jira/browse/TAMAYA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255082#comment-14255082
]
Anatole Tresch commented on TAMAYA-35:
--------------------------------------
my first question is, what is the purpose and packaging of this provider, is
the idea to
- add it to core and register it automatically, if yes, under which name? When
it should replace the _default_ I would start with the default provider
existing and discuss, if we need additional folders, resources etc.
- or should it be added as separate provider module that can be added as a
dependency, hereby registering for _default_ (or even controlled by a system
property)?
Content wise:
- is it wise just to add every kind of path users might want to use? IMO one is
sufficient, if no you also add
{{META-INF/configuration, cfg, config, tamaya, Configuration, ... }} . If you
want to define your own, you can still add your own provider.
- additionally it would also be possible to make the default (simple) provider
configurable, so you can define with {{-Dtamaya.configbase}} the classpath root
locations, you want to use.
WDYT?
> 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
>
> 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)
