[
https://issues.apache.org/jira/browse/TAMAYA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255186#comment-14255186
]
Anatole Tresch commented on TAMAYA-35:
--------------------------------------
As I said: can we should start a thread on dev first. Basically I would try to
outline the use case and requirements first, so we all have the same
understanding before hacking away a provider. All the things you said, like
automatic reload are great and definitively must be supported, but I would want
first to figure out the basic mechanism of automatic reloading (also as a proof
of concept of the API/SPI in place currently), report and fix together any
issues encountered. With that we get an additional important tool to the
backing functionality, hopefully in a isolated/reusable form (how about a
*observable resource as a pattern?*). Then
we can talk about what would be a reasonable default and what kind of providers
(aka metamodels) should be provided by Tamaya OOTB and what not.
> 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)
